This message was deleted.

sparse-intern-71089

09/30/2022, 12:04 PM

This message was deleted.

echoing-dinner-19531

09/30/2022, 1:15 PM

Oh yeh that’s probably a new bug. We don’t really need a project for destroy at the moment because we don’t actually run the program for it, so we added a trick to just return an empty project if we couldn’t find a Pulumi.yaml. But now the project loader validates that Pulumi.yaml has the expected shape, and empty is not valid. Probably an easy fix, if you roll back a couple of versions it should work for now and I’ll see about getting a fix in for this in time for the next release.

echoing-dinner-19531

09/30/2022, 1:17 PM

Also might be worth checking that you don’t have an empty Pulumi.yaml around. That would trigger this

echoing-dinner-19531

09/30/2022, 1:21 PM

Actually going and checking the code for this I think it can only be triggered by an empty Pulumi.yaml, our “empty project” is created post-validation.

kind-napkin-54965

10/01/2022, 6:01 PM

Thanks Fraser! I indeed had an empty Pulumi.yaml lying around. Now I am able to get the

pulumi destroy

as well as

pulumi stack rm

. Thanks a ton!!

17 Views

Open in Slack

Previous Next

Pulumi Community

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.