-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(CLI): change-set diff not required for new stack diffs #29268
Closed
Closed
Changes from 11 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
bf7c7bb
add check for new stak in fullDiff function
sumupitchayan ec2fe4e
add unit test
sumupitchayan f578824
fix diff test expect
sumupitchayan f793b87
expect NewResource change impact to be WILL_CREATE in test
sumupitchayan cedf900
Merge branch 'main' into sumughan/fix-changeset-delete-stack
sumupitchayan 400147e
fix diff test string problems in test expect
sumupitchayan 4df1cf0
Merge main
sumupitchayan 0d2fc04
Merge branch 'main' into sumughan/fix-changeset-delete-stack
sumupitchayan bcb544c
try fixing migrate import diff in cdktoolkit
sumupitchayan 01071bd
Revert changes to import test expect
sumupitchayan d4cb526
Merge branch 'sumughan/fix-changeset-delete-stack' of https://github.…
sumupitchayan 7b678ca
add important info for all changeSets, just don't do filterFalsePosit…
sumupitchayan bb73010
Revert "try fixing migrate import diff in cdktoolkit"
sumupitchayan c94c8ae
Merge branch 'main' into sumughan/fix-changeset-delete-stack
sumupitchayan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might be missing something but I'm not sure how this tests that we do not do a changeset for new stacks. Could you clarify that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was confused on this too - my logic was that calling
fullDiff
with the current stack being empty (new) should mean that there should be only 1 difference count, and the change impact should beResourceImpact.WILL_CREATE
; I'm not sure how else to test that we don't do changeset for new stacks