little-cartoon-1056905/15/2022, 9:42 PM
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?
.. is there an example of that anywhere?
. 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.
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-7812005/15/2022, 9:49 PM
little-cartoon-1056905/15/2022, 9:53 PM
brainy-church-7812005/15/2022, 9:57 PM
little-cartoon-1056905/15/2022, 10:10 PM
brainy-church-7812005/15/2022, 10:12 PM
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-1056905/15/2022, 10:12 PM