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: `cdk init` fails if run under a directory where `cdk.json` exists
See original GitHub issueI have a messy ~/Temp directory where I try out all kinds of things.
It so happens that ~/Temp/cdk.json exists, but what happens since https://github.com/aws/aws-cdk/pull/5772 is that I can’t run cdk init anymore anywhere under ~/Temp, which I do all the time:
huijbers ~/Temp> cd cdk-java-app/
huijbers ~/T/cdk-java-app> cdk init --language=java
'cdk init' cannot be run in a non-empty directory!
Well the directory is empty! I just made it!
Turns out that the CLI chdir()s to ~/Temp before cdk init is run, but it’s super hard for me to figure that out.
Can I suggest that the magic chdir behavior only happens when applicable to an existing CDK app, for commands like synth and deploy etc?
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 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
I would argue this is not really a p0 though.
I am closing this issue since the feature that caused this bug was reverted in version
1.21.1.