Honor log_request_body setting in compliance audit log #31
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.
Description
This PR ensures that the value of
log_request_body
is honored for the compliance logging. When using the compliance config, this PR will ensure that the document's source is audit logged in theaudit_request_body
when a document is first created, but otherwise it will not. Whenwrite_log_diffs
is enabled, you can trace the full history of changes to documents on the tracked indices by looking for all events on the target index.By default, the security index gets events audit logged so Compliant logging is a good feature to use to trace changes to the security configuration.
Enhancement
Issues Resolved
opensearch-project#4534
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.