This message was deleted.
# typescripts
sparse-intern-71089
05/30/2023, 12:56 PMThis message was deleted.
a
astonishing-exabyte-93491
05/30/2023, 7:26 PMHi,
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 PMAnother 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>'a
able-flag-79751
05/30/2023, 7:47 PMThanks @astonishing-exabyte-93491. I’ve been able to solve that issue. I have new issues:
able-flag-79751
05/30/2023, 7:48 PMI can’t delete them manually from the AWS console either. I will appreciate any direction on this
a
astonishing-exabyte-93491
05/30/2023, 7:48 PMDependency problems are nightmare.
🥲 1
astonishing-exabyte-93491
05/30/2023, 7:50 PMThis 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 PMIf you have properly set the resource dependencies, then you could run:
Copy code
#!/bin/bash
$ pulumi destroy -t <parent-resource-urn> --target-dependents2 Views