[CORL-1291] Logging Improvements #3103
Merged
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
tessalt
reviewed
Aug 13, 2020
|
That’s true. This is a stop gap until we’re able to replace our settings update mutations with more discrete mutations that would let us apply auditing on the mutation/schema level. |
tessalt
approved these changes
Aug 14, 2020
wyattjoh
added
the
🚀 merge it!
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.
What does this PR do?
Whenever settings are updated, log the fields being updated as well as the user performing the action.
What changes to the GraphQL/Database Schema does this PR introduce?
None.
How do I test this PR?
Update settings, see the new log entry:
settings update audit.