I have a stuck deployment that was kicked off from CI GitHub

Question

I have a stuck deployment that was kicked off from CI GitHub action It has failed because of invalid resource combinations in the target AWS environment but now it s just sitting there waiting for a `pulumi cancel` or similar Since I don t have command line access to this stack it s all locked down via OIDC only that particular GitHub branch can control this stack what s the suggested way of cancelling this deployment

little-cartoon-10569 · Answer

I d really like a Cancel button in the deployment s pane in the Activity tab as that would just work

little-cartoon-10569 · Answer

Failing that I could set up a special PR or gitops thing to run `pulumi cancel` is there an example of that anywhere

little-cartoon-10569 · Answer

And the last option would be to set up a back door in the OIDC connectivity another role that allows access from dev machines to run `pulumi cancel` This would be the most general purpose solution but would also be our last choice If we re able to have a robust deployment strategy that forbids all unplanned manual access that s what we d prefer

little-cartoon-10569 · Answer

A timeout option on a `pulumi up` would also work for us Since we know how long a full deployment takes we can use that information at deployment time to get Pulumi to auto cancel when we go significantly longer Is that a feature

brainy-church-78120 · Answer

docs on custom timeouts <https www pulumi com docs intro concepts resources options customtimeouts >

little-cartoon-10569 · Answer

Thanks That s a per resource timeout We can configure that on the offending resource this time since we now know that that s a potential problem But it won t be a general fix unfortunately Is there an equivalent for an entire `pulumi up`

brainy-church-78120 · Answer

ah k i see i dont believe we have something for the entire update

little-cartoon-10569 · Answer

I think a feature request for a cancel button is probably best That d be pretty useful in quite a few cases

little-cartoon-10569 · Answer

And I can also put a timeout in our GitHub workflow that calls `pulumi cancel` locally

brainy-church-78120 · Answer

gt I think a feature request for a cancel button is probably best That d be pretty useful in quite a few cases i agree mind opening up an issue in <https github com pulumi service requests issues>

little-cartoon-10569 · Answer

Will do

little-cartoon-10569 · Answer