This message was deleted.

sparse-intern-71089

05/30/2023, 12:56 PM

This message was deleted.

astonishing-exabyte-93491

05/30/2023, 7:26 PM

Hi, The way to go here is to identity the URNs of the resources you deleted manually, and then remove them from your pulumi state.

Copy code

$ pulumi stack --show-urns | grep <regex-used-to-identify-resource>
# Then having identified the resource URN
$ pulumi state delete '<resource-urn>' # use single quotes to prevent param expansion as resources urns may contain '$'s.

astonishing-exabyte-93491

05/30/2023, 7:27 PM

Another possibility is to refresh your stack state, pulumi should then become aware of the resources that have been deleted.

Copy code

$ pulumi refresh
# or pulumi refresh -t '<resource-urn>'

able-flag-79751

05/30/2023, 7:47 PM

Thanks @astonishing-exabyte-93491. I’ve been able to solve that issue. I have new issues:

able-flag-79751

05/30/2023, 7:48 PM

I can’t delete them manually from the AWS console either. I will appreciate any direction on this

astonishing-exabyte-93491

05/30/2023, 7:48 PM

Dependency problems are nightmare.

🥲 1

astonishing-exabyte-93491

05/30/2023, 7:50 PM

This is the AWS API returning a client error. It’s best practice to handle your resources lifecycle using pulumi only, instead of making manual interventions. The error looks pretty straighforward. Would you mind sharing your code?

astonishing-exabyte-93491

05/30/2023, 7:52 PM

If you have properly set the resource dependencies, then you could run:

Copy code

#!/bin/bash
$ pulumi destroy -t <parent-resource-urn> --target-dependents

but I’m not confident enough this is your case.

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.