cdk diff does not work with nested stacks
See original GitHub issueRunning cdk diff
only lists the S3 templates of the root stack as changed.
Reproduction Steps
Create a nested stack with some resources in a nested stack. Deploy the nested stack. Add more resources to nested stack.
cdk diff
should report the changes in the nested stack.
Error Log
N/A
Environment
- CLI Version : 1.19.0
- Framework Version: 1.19.0
- OS : macOS
- Language : TypeScript
This is 🐛 Bug Report
Issue Analytics
- State:
- Created 4 years ago
- Reactions:55
- Comments:19 (10 by maintainers)
Top Results From Across the Web
Can't get diff output from NestedStack in AWS CDK
This commit adds a workaround where you can run cdk deploy --no-execute. and then view the nested stack changes in the CloudFormation change ......
Read more >CDK and nested stacks : r/aws - Reddit
I'm asking because CDK provides the ability to "replicate" stacks easily through code, which is kind of what nested stacks look like they...
Read more >Stacks - AWS Cloud Development Kit (AWS CDK) v2
Nested stacks are bound to their parent stack and are not treated as independent deployment artifacts. They aren't listed by cdk list ,...
Read more >Using Nested Stacks with AWS CDK - DEV Community
A basic example of how Nested Stacks work in AWS CDK. Do not forget to destroy this stack after you're done via: yarn...
Read more >@seed-run/aws-cdk - npm
Importing resources in nested stacks is not possible. Uses the deploy role credentials (necessary to read the encrypted staging bucket).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi everyone!
Sorry for not providing an update for a while. This is not currently being worked on, and currently not planed. The label
p1
means it is something we want to add to the AWS CDK, and it will get a higher priority in our planing. As for the “when”, I don’t have an answer, we are currently focused on v2 and it is unlikely we will get to this before v2 release.@cmckni3 It does! I will look into what is required to add this to the cdk. Thanks!