-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide option to not fail a destroy when the stack doesn't exist #1001
Comments
Would it be possible to run a "pulumi stack select" first and if that fails ignore and skip the destroy?
|
I mean this issue is specifically about the action; if I was using the CLI directly I would have it solved already. |
🤦♂️ I didn't even notice what repo I was in. Yes something like this sounds reasonable. |
Ah, yes I suppose it could also apply to updates, so long as upsert isn't given (both as it's nonsensical and also to avoid passing if the stack create fails for some reason). |
Hello!
Issue details
We have a workflow that destroys a Pulumi stack when a PR is closed. However, not all PRs get deployed. For those, the destroy workflow fails. While not critical, this is still annoying and means if there's an actual error, it likely won't be caught as people are effectively trained to ignore errors on this workflow.
We'd like to have an option, eg
ignore-missing-stack: boolean
that does exactly this.Affected area/feature
The text was updated successfully, but these errors were encountered: