Closed remorses closed 2 years ago
i managed to fix my state with pulumi state delete urn:pulumi:production::xxx-gcp-cloudrun::gcp:cloudrun/iamPolicy:IamPolicy::noauthIamPolicy
Hi @remorses - sometimes when a Pulumi stack gets out of sync with its backend, this can happen - in case you weren't aware, we have Pulumi Refresh for that situation!
Thank you for sharing your workaround as well. 🙇♀️
@guineveresaenger pulumi refresh
did not work
Pulumi was detecting that the service was deleted but not the iam policy
ah! that makes sense - so I have one more suggestion for the future for you:
If resources are dependent on one another, you can denote that relationship with a parent
resource option.
This wouldn't've helped in this case since relationships must be established before reconciliation attempts with your stack, but it may be something for you to look into.
What happened?
Pulumi tries to delete
gcp:cloudrun:IamPolicy
even if it is already deletedI manaully deleted a cloud run service, pulumi detects that the service is deleted but tries to delte the iam policy (which no longer exists)
Steps to reproduce
Expected Behavior
it should not try to delete a deleted resource
Actual Behavior
fails with
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).