RANGER-3937: [Docker] Add capability to run ranger plugins and services with their own versions #215
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?
Currently, the versions of ranger plugins and services(including ranger usersync and ranger tagsync) present as part of the respective ranger-service images are based on the ranger admin version whereas they can have their own versions independent of ranger admin version. This will allow ranger plugins to interact with ranger while being on different versions.
for ex: ranger-hadoop and ranger-hive images run with plugin version 2.2.0 whereas ranger-admin image runs with version 2.3.0.
How was this patch tested?
All containers come up fine
Test connection successful
Policies synced to plugin(seen from Plugins tab in ranger UI)
Versions across containers visible here: