You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(integ-runner): disable update workflow by default (#951)
I've lost 2 hours
debugging why my deployment was failing trying to deploy to nonexistent
and non-requested accounts and regions, and the
answer was: the checked-in snapshot was nonsensical, and the update
workflow will first deploy the checked-in snapshot and only then deploy
the current snapshot.
Good idea, bad execution: if existing
snapshots are not region-agnostic they are guaranteed to fail. We should
probably resynthesize them from the previous git commit instead.
Whatever it is, what we do right now doesn't work so I'm disabling the
default.
Turn `--disable-update-workflow` into `--[no-]update-workflow`, with the
default being `false`.
---
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license
.option('strict',{type: 'boolean',default: false,desc: 'Fail if any specified tests are not found'})
41
41
.options('from-file',{type: 'string',desc: 'Read TEST names from a file (one TEST per line)'})
42
42
.option('inspect-failures',{type: 'boolean',desc: 'Keep the integ test cloud assembly if a failure occurs for inspection',default: false})
43
-
.option('disable-update-workflow',{type: 'boolean',default: false,desc: 'If this is "true" then the stack update workflow will be disabled'})
43
+
.option('disable-update-workflow',{type: 'boolean',default: undefined,desc: 'DEPRECATED, use --[no]-update-workflow instead'})
44
+
.option('update-workflow',{type: 'boolean',default: undefined,desc: 'Deploys the committed snapshot before the updated application. Only works if snapshots are region-agnostic.'})
0 commit comments