RANGER-5230: add configuration to force policy engine to update its p… #669
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…olicy cache synchronously
What changes were proposed in this pull request?
Cherry-pick of 6a812eb from master branch with the required code changes to account for code divergence between the two branches
Proposes new config set via service plugin configs (repo configs) ranger.plugin.<service_name>.policy.refresh.synchronous=true that can be used to synchronously download policies during policy evaluation to reduce time waiting for plugin tests to download latest policies
How was this patch tested?
Manually tested.
Docker containers come up
Policies are evaluated synchronously