I'm submitting a ...
What is the current behavior?
If the current behavior is a :beetle:bug:beetle:: Please provide the steps to reproduce
When you specify profile in cdk.json, it's ignored.
profile key is respected.
Having reasonable defaults for a project. The ultimate ideal would be per-env credentials but we're using multiple cdk.json files (one per account) as a stopgap.
Please tell us about your environment:
I've experienced the same issue. Following this I was under the impression that adding profile to cdk.json should work, but it doesn't.
If that worked, for me that would be a major improvement since I have multiple profiles I currently have to specify --profile option with every cli command.
@prencher @boricic - I don't believe we support all the switches in cdk.json and we should. tagging this as a bug
Hi, thanks for solving it!
Is it a part of 1.36.1? The ckd.json->profile still doesn't seem to affect my npx cdk calls
Hi, thanks for solving it!
Is it a part of
1.36.1? Theckd.json->profilestill doesn't seem to affect mynpx cdkcalls
it will be included in the next release (likely 1.37.0)
Most helpful comment
I've experienced the same issue. Following this I was under the impression that adding
profiletocdk.jsonshould work, but it doesn't.If that worked, for me that would be a major improvement since I have multiple profiles I currently have to specify
--profileoption with every cli command.