RakeshGuptaDev opened a new pull request, #1356: URL: https://github.com/apache/ranger/pull/1356
## What changes were proposed in this pull request? The fix for the typo "Type Catagory" → "Type Category" introduced in https://issues.apache.org/jira/browse/RANGER-4805 ([ranger-servicedef-atlas](https://issues.apache.org/jira/browse/RANGER-servicedef-atlas).json) is applied only during fresh installations. During an upgrade, the Ranger UI continues to display the old typo because resource labels are retrieved from the x_resource_def database table, which retains the pre-upgrade values. and After [RANGER-4805](https://issues.apache.org/jira/browse/RANGER-4805), Atlas permissions (atlas:read, etc.) can still appear in tag policies and in x_access_type_def, especially after [RANGER-3491](https://issues.apache.org/jira/browse/RANGER-3491) changed the service-definition bootstrap flow. Cause: The enableTagBasedPolicies check was only present in updateTagServiceDefForAccessTypes(), which is no longer called from the production code. The actual sync path (postCreate / postUpdate → updateTagServiceDefForUpdatingAccessTypes()) did not have this check, allowing Atlas permissions to be synced into the tag service-definition. ## How was this patch tested? - Verified that the updated resource labels and descriptions from the service definition JSON are correctly synchronized to the x_resource_def table during an upgrade. - Verified that the Ranger UI displays the updated "Type Category" label after upgrading an existing Ranger installation. - Tested upgrade with J10071 patch; verified atlas:* absent from x_access_type_def and tag policy UI. Restarted Ranger Admin and updated Atlas service-def — Atlas permissions did not reappear. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
