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.
cdk cli always exits with code 1 when doing a diff
See original GitHub issueCDK cli always exits with code 1 even if the result is the expected (getting a list of possible changes). This behaviour makes it hard to integrate with CI tools like GitLabCi. Exit code 1 should be expected if eg. AWS permission error for the command execution occured but not if there are outstanding changes.
Reproduction Steps
do a cdk diff in any project using aws-cdk
What did you expect to happen?
Get a list of possible changes and exit code 0 if no error during the command occured
What actually happened?
cdk diff always exits with code 1, which makes it hard to use in tools like gitlabci pipelines
Environment
- CLI Version : 1.60.0 (build 8e3f53a)
- Node.js Version: v14.7.0
- OS : MacOS Catalina 10.15.6
- Language (Version): all
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@shivlaks @jonny-rimek i set the property inside the context, passed it via CLI and added it to the cdk.json however still exits with 1. I tried it on other projects eg. the official examples and indeed it behaved as expected and exits with code 0.
This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.