[AMBARI-22725] Expose Conditional Elements For Tasks on Upgrade #84
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?
I decided to break out the work of having condition tasks with upgrading Kerberos-related properties (see AMBARI-22803 for the RPC/Kerberos related work)
Some upgrade tasks, such as configuration tasks, need to leverage the conditional elements which change the flow of control if the cluster is Kerberized (or based on other configuration values). For example, today we have this:
Where
condition
elements can be added to anexecute-stage
or agroup
. However, sinceexecute-stage
may only contain one task, it makes doing this work on a per-task level impossible. This particularly impacts theprocessing
element. We want something like this:So that
task
elements defined in thepre-upgrade
section ofprocessing
can also be conditionally invoked.How was this patch tested?