Madhan Neethiraj created RANGER-4769:
----------------------------------------
Summary: Admin audit generation: replace implementation logic in
13 classes to couple of base classes
Key: RANGER-4769
URL: https://issues.apache.org/jira/browse/RANGER-4769
Project: Ranger
Issue Type: Sub-task
Components: Ranger
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
When an object (like policy, security-zone, role) is updated, admin audit logs
are generated with the details of the updated attributes. The logic to compute
updated attributes is implemented in 13 classes, as listed below:
# RangerPolicyService.getTransactionLog()
# RangerRoleService.getTransactionLog()
# RangerSecurityZoneServiceService.getTransactionLog()
# RangerServiceService.getTransactionLog()
# RangerGdsBaseModelService.createTransactionLog()
# XAssetService.getTransactionLog()
# XAuditMapService.getTransactionLog()
# XGroupService.getTransactionLog()
# XGroupUserService.getTransactionLog()
# XPermMapService.getTransactionLog()
# XPortalUserService.getTransactionLog()
# XResourceService.getTransactionLog()
# XUserService.getTransactionLog()
To avoid unnecessary code duplication, consider moving implementations in above
classes to their base class - like RangerBaseModelService and
AbstractBaseResourceService.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
