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
feat(cli): control progress output style with --progress=bar|events (#9623)
Since the new deployment monitoring has been problematic on environments such as CI,
adding a switch called `progress` to allow users to set their deploy output display preference.
Supported values are `bar` and `events`. The default deployment display mode includes the
progress bar.
The workaround of adding `-v` to display the stack event history includes a lot of
undesired output and users have expressed that it includes a lot of noise.
If the key `progress` exists in user settings (`~/.cdk.json`) or project settings (`cdk.json`),
users will not need to specify it on every deploy and can set their desired default once.
closes#8696
----
*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@@ -89,7 +90,8 @@ async function parseCommandLineArguments() {
89
90
.option('force',{alias: 'f',type: 'boolean',desc: 'Always deploy stack even if templates are identical',default: false})
90
91
.option('parameters',{type: 'array',desc: 'Additional parameters passed to CloudFormation at deploy time (STACK:KEY=VALUE)',nargs: 1,requiresArg: true,default: {}})
91
92
.option('outputs-file',{type: 'string',alias: 'O',desc: 'Path to file where stack outputs will be written as JSON',requiresArg: true})
92
-
.option('previous-parameters',{type: 'boolean',default: true,desc: 'Use previous values for existing parameters (you must specify all parameters on every deployment if this is disabled)'}),
93
+
.option('previous-parameters',{type: 'boolean',default: true,desc: 'Use previous values for existing parameters (you must specify all parameters on every deployment if this is disabled)'})
94
+
.option('progress',{type: 'string',choices: [StackActivityProgress.BAR,StackActivityProgress.EVENTS],desc: 'Display mode for stack activity events.'}),
93
95
)
94
96
.command('destroy [STACKS..]','Destroy the stack(s) named STACKS',yargs=>yargs
95
97
.option('exclusively',{type: 'boolean',alias: 'e',desc: 'Only destroy requested stacks, don\'t include dependees'})
@@ -279,6 +281,7 @@ async function initCommandLine() {
0 commit comments