question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[CLI] display issues with new deployment monitoring in the CDK CLI

See original GitHub issue

_Originally posted by @robertd in https://github.com/aws/aws-cdk/pull/8165#issuecomment-647178526_

It’s not working really well on iTerm2 with zsh (using robbierussel/oh-my-zsh)?

Is there a way to use more verbose output (~for CI/CD purposes too~)?

➜  sipp-api-cdk git:(master) ✗ cdk deploy
SippApiStack: deploying...
SippApiStack: creating CloudFormation changeset...








 ✅  SippApiStack

Outputs:
SippApiStack.ServiceServiceURL250C0FB6 = https://sipp-api-alb.acme.com
SippApiStack.ServiceLoadBalancerDNSEC5B149E = internal-SippA-Servi-1X2ZSXSR3W328-1234567890.us-west-2.elb.amazonaws.com

Stack ARN:
arn:aws:cloudformation:us-west-2:1234567890:stack/SippApiStack/3841b3e0-b271-11ea-aae2-065639e88e5c

. . .

edit: Luckily everything looks fine in Gitlab’s CI/CD pipeline.

image

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:2
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

6reactions
blimmercommented, Jun 30, 2020

Agreed. In addition to providing an option for people to choose, I think non-interactive terminals (like CI) should default to the other output style. Most (all?) CI platforms set the CI environment variable, so maybe when the CI variable is set (or another non-interactive terminal is detected), CDK automatically reverts to the old behavior?

6reactions
nija-atcommented, Jun 23, 2020

_Originally posted by @slotnick in https://github.com/aws/aws-cdk/pull/8165#issuecomment-647998179_

Encountering exactly the same here. Is there an option to disable this mode and revert to the previous display? It’s also useful to understand what happened during the build, which is lost with this update. My working model is to kick off a build, then check back after awhile to see what happened. This change makes that very difficult.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting common AWS CDK issues
This topic describes how to troubleshoot the following issues with the AWS CDK. After updating the AWS CDK, the AWS CDK Toolkit (CLI)...
Read more >
@seed-run/aws-cdk - npm
If a resource fails to be created or updated, the deployment will roll back before the CLI returns. All changes made up to...
Read more >
Datadog CDK Construct
Use this Datadog CDK Construct Library to deploy serverless applications using AWS CDK . This CDK library automatically configures ingestion of metrics, ...
Read more >
AWS CDK CLI | Docs | Buddy: The DevOps Automation Platform
Get Started. Sign up for free and deploy your project in less than 10 minutes. GitHub ...
Read more >
Introduction to CDK - Activate Early stage path
The AWS Cloud Development Kit (CDK) is a new software development framework from ... In this phase the AWS CDK CLI takes the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found