cli: organize output from CDK deploy with concurrency

[polothy]

Describe the feature

Current behavior of a command like:

cdk deploy --all --concurrency 10

Is that all of the concurrent or parallel deployments stream to Stdout/Stderr at the same time. This makes it really difficult to see what is happening because progress is mixed between 10 stacks being deployed.

I have not see what happens in case of an error (I think I read somewhere it'll re-print?), but was thinking it might be hard to adopt this if I cannot figure out what happens on deployment failure.

Use Case

Reason for this feature request: being able to clearly understand what is happening during the deployment and (more importantly) to be able to debug when a deployment failure happens.

If deployment errors are re-printed clearly without intermixing multiple deployments, we can probably close this issue.

Proposed Solution

Buffer the output of each deployment and only print to Stdout/Stderr when the deployment is done/failed.

Could also print other progress information, like "Deploying stack {stackName} ({stackId}) 2 of 10 stacks"

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.93.0

Environment details (OS name and version, etc.)

macOS

[khushail]

Hi @polothy , I am not clear about your requirement here. I tried deploying 3 stacks in parellel and reproduced this output for deployment failure , to share with you. Here we can see each stack name ,with its status and reason of failure.

Could you please share more about your requirement as what you want to see and what is missing here ?

[polothy]

First, thank you for trying this and posting a screenshot - this was really helpful.

I think I misinterpreted the output. It appears that while some things are mixed, the deployment status updates appear to be grouped. I'll re-try this and see how it goes.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.