Allow extra parameters when playbook is defined in configuration/settings file #1474
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.
Summary:
With this, all the parameters that are not directly supported by ansible-navigator and usually used via a
--
delimiter, can also be used when playbook is defined in the navigator's settings file.This will allow
ansible-navigator run
to support extra parameters when playbook is specified in the configuration (instead of command itself)Example:
ansible-navigator run -- -e my_var=value
When configuration can be something like :
Fixes: #1437