Normalize policy JSON before diffing #4
Conversation
This file contains hidden or 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
Indent() only changes whitespace, Unmarshal+Marshal is necessary for keys to be sorted.
- display the field name before the diff - special-case the case when there is no difference (for example another attribute change is forcing an object recreation)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 ap
2CE2
plied 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.
Currently, Astro uses Indent(), which only changes whitespace:
Unmarshal+Marshal is necessary for keys to be sorted.
To avoid confusion, the case when old and new policies are the same
after normalization still shows the field as modified with an explanatory
message, and there is a command-line switch to disable policy diffing.