I've just noticed that cdk diffis not displaying the ChangeSet in the AWS CF Console.
Why ? Any reason for that ?
( seeing the ChangeSet in AWS CF Console history is too late with cdk deploy)
I like seeing the changes in console using cdk diffbut they should be identical to what I should be visualising in AWS CF ChangeSet before applying them. Are they identical ?
daily scenario: updating existing Stacks in various environments
I don't want to check the ChangeSet history but I would like to check prior to applying the changes with cdk deploy
cdk diff just this command or with a flag to display the ChangeSet details also in AWS CF ChangeSet Console
This is a :rocket: Feature Request
I'm interested in this too.
I would love to be able to deploy a Change Set to a stack, without executing the changes. Basically I would like to see what will change through AWS CloudFormation service, and then execute or discard the changes.
cdk deploy STACK creates a Change Set AND applies the changes.
I would love to have an option that will create the Change Set (so I can visualise it in AWS CloudFormation) and not apply the changes.
Something like cdk deploy STACK --execute-change-set no.
I can see where this can be useful. How would that work with multi-stack apps? Will it create a changeset for all of them?
As for the name of the switch, I think --execute and --no-execute should be sufficient and --no-execute should print the link to the change set of course!
hi @eladb,
yes, each Stack with its own ChangeSet, perfectly fine also with the options you mentioned.
That will be awesome and one more step closer to production ready as I see it.
Toda Raba.
Related to #3780
Great job guys!
Many thanks @robertma96 @SomayaB @eladb
Can鈥檛 wait to use this in the future release.
Most helpful comment
Great job guys!
Many thanks @robertma96 @SomayaB @eladb
Can鈥檛 wait to use this in the future release.