This message was deleted.
# pulumi-cloud
s
This message was deleted.
l
I'd really like a "Cancel" button in the deployment's pane in the "Activity" tab, as that would just work.
Failing that, I could set up a special PR or gitops thing to run
pulumi cancel
.. is there an example of that anywhere?
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.
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?
b
l
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
?
b
ah k, i see. i dont believe we have something for the entire update
l
I think a feature request for a cancel button is probably best. That'd be pretty useful in quite a few cases.
And I can also put a timeout in our GitHub workflow that calls
pulumi cancel
locally.
b
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
l
Will do
🙏 1