feat: implement auditing metadata support for Datastore #534 #4271
+147
−98
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
mehdi0933
force-pushed
the
feat/datastore-auditing-534
branch
from
2cbe40b to
22085e8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 addresses issue #534 by adding auditing metadata support for Cloud Datastore.
Changes
DatastorePersistentPropertyandDatastorePersistentPropertyImplto recognize Spring Data auditing annotations:@CreatedDate,@LastModifiedDate,@CreatedBy, and@LastModifiedBy.DatastoreMappingContextto include anauditingEnabledflag.DatastoreMappingContextTeststo verify that@CreatedDateproperties are correctly identified by the mapping context.Impact
This allows the Datastore module to integrate with Spring Data's auditing framework, enabling automatic population of creation and modification dates/users.