"cdk diff" should take assets into account
See original GitHub issueWhen running cdk diff
, the toolkit should take assets into account. At the moment, if only assets change, “cdk diff” will show no differences, but “cdk deploy” will update the stack since the asset’s md5 changes.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:26
- Comments:5 (2 by maintainers)
Top Results From Across the Web
DefaultStackSynthesizerProps - AWS Documentation
The role to use to publish file assets to the S3 bucket in this environment. You must supply this if you have given...
Read more >AWS CDK Toolkit - npm
cdk diff, Diff stacks against current state. cdk deploy, Deploy a stack into an AWS account. cdk destroy, Deletes a stack from an...
Read more >Deploying your CDK app to different stages and environments
This property receives the account id and the region for this stack. If you do not want to configure the real target data...
Read more >Hey CDK, how do cross-account deployments work?
As soon as you start using assets in your CDK application, you need to bootstrap your AWS account. Assets could be files or...
Read more >Lessons in AWS Python CDK: 1-Getting Started
If you are using Homebrew for everything else, you might as well use it to install the CDK as well. You can also...
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 FreeTop 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
Top GitHub Comments
For a quick and dirty hack I just inject a hash of the asset into the stack somewhere, in the case of a lambda just set an environment variable. Then when running
cdk diff
it’s obvious what will update.will be fixed by #2821