Non-sensitive diff support for credential history #231
Conversation
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
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 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.
This change modifies the behavior and data in the history view for credentials, to remove sensitive information from that view. A new diff_credential endpoint has been added, which will take two revisions for a credential ID, and returns a non-sensitive diff of the two credentials.
The history view for the credential shows a -/+ view of the two credentials, side-by-side. For credential_pairs (the sensitive part), it shows what's been added and removed, by credential_pair key. In the case a credential pair has been modified, it'll show as being removed and added (similar to a git diff).