No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

It should be possible to destroy any stack by passing the `--stack` (or `-s`) option — for example, `pulumi destroy -s myorg/myproject/mystack`. Have you tried this?

yes i tried that but it still try to find a *Pulumi.yaml* which does not exist on the file system since the *s*tack was created with the *Pulumi Automation API*

Are you using the Pulumi Cloud backend or a self-managed one? (I don’t think this should matter, but worth asking nonetheless.)

Using Pulumi Cloud. Seems that Pulumi CLI needs a *Pulumi.yaml* in order to do `pulumi destroy -s` , while it does *NOT* need a *Pulumi.yaml* to do `pulumi rm -s`   on stacks that were originally created with *Pulumi Automation API*

Are you running the command from a directory that is a descendant of a directory containing a Pulumi.yaml file? I think I’ve seen that there’s a quirk in the CLI behavior where running this command will fail when run within a non-matching project dir.

Ah ok, indeed, i ran it from a deep directory that had Pulumi.yaml somewhere in an ancesstor directory... I 'll try to run it from a Pulumi agnostic folder...