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

I keep getting this after a failed pulumi update that uses nested Pulumi components.

The update will fail to create resources and deletes the parent resource without deleting the dependencies. This then causes subsequent update attempts to fail with that error

that’s a bug in Pulumi , unfortunately - what version of Pulumi are you using, and do you have a repro for this?

You can repair your stack by using <https://pulumi.io/reference/cli/pulumi_state_delete.html> to delete any resources from your checkpoint that the CLI is complaining about, but you will need to delete those resources manually (e.g. in your cloud provider’s console).

hmm, that’s unfortunate. Can you open an issue?

Yeah, it will be a bit tough to give an exact example to reproduce this but I’ll try to get to it this week.

thank you! let us know if we can help at all with getting your stack back into a good state, although this scenario is exactly what we had in mind when we created `pulumi state delete`

see also: <https://pulumi.io/reference/troubleshooting.html#editing-your-deployment>

ive been editing state files manually, glad to see `delete` is implemented

yeah - ideally people never have to do that by hand :laughing:

hmm, whats the syntax for the resource item after `pulumi state delete`? using the full URN doesn’t work