Use escalate privilege setting in ansible services and automate methods #19012
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.
This adds a new option for ansible runner for whether to attempt to escalate privileges during the playbook run.
A side-effect of this is that the credential no-longer determines whether the
--become
arg is passed in the command line hash rather it is only passed if ansible runner is given:become_enabled == true
. The credentials will provide their privilege escalation passwords unconditionally.The second commit passes the option from services and automate methods to the ansible runner invocation.