Ranger 5628 - Support for actions in Ozone Service Definition#995
Open
fmorg-git wants to merge 5 commits into
Open
Ranger 5628 - Support for actions in Ozone Service Definition#995fmorg-git wants to merge 5 commits into
fmorg-git wants to merge 5 commits into
Conversation
added 5 commits
June 3, 2026 14:54
Generated-By: Cursor, Claude Code and then with additional manual updates.
Generated-By: Cursor, Claude Code and then with additional manual updates.
Generated-By: Cursor
…ions, and ensure actions wrap around instead of scrolling horizontally indefinitely. It also fixes latent React hook violations of having useState within a conditional (CommonComponents.jsx) and a loop (Editable.jsx). It also ensures that the action field only shows up in the Policy Conditions section, not on the overall Resource Policy. Generated-By: Cursor, Claude Code
Generated-By: Cursor, Claude Code
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
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.
What changes were proposed in this pull request?
For upcoming Ozone STS feature, we need the ability to identify what actions are allowed for an STS token (ex GetObject, GetObjectTagging, PutObject, etc), in addition to the less granular existing permission system (read, write, create, etc). This ticket updates the Ranger policy evaluation to keep the existing permission evaluation for legacy reasons, and add optional action evaluation via policy condition in the UI. If the resource policy has an action and an action is supplied in the RequestContext, they must match (in addition to the permissions). If no action is identified in the resource policy, then all actions are allowed and only the permissions are required.
Also there are several UI updates:
CommonComponents.jsx) and a loop (Editable.jsx).The UI updates are implemented in a way such that the hdfs service definition can later make use of the filtering actions by permissions behavior.
The majority of this code was generated with Cursor and Claude Code, with some manual modifications afterward by me. I have broken into reviewable commits - please let me know if this needs to be more than one PR.
https://issues.apache.org/jira/browse/RANGER-5628
How was this patch tested?
manual testing locally in Ranger docker, also end-to-end smoke tests locally with Ozone and Ranger