What problems exist that this proposal will solve?
Currently there is no way to define variables exclusively for a playbook. Group vars is undesirable because it can affect multiple playbooks and --extra-vars means you can't store the variable in the yaml if you want to. There is a clear use case for passing the same variable into multiple import-playbook calls.
Contrary to this, playbook variables don't actually exist. This is a variable defined on a play.
Proposal: Playbook level variables:
e.g. vars: url: example.com
import_playbook: cluster_services.yml import_playbook: cluster_services.yml import_playbook: cluster_services.yml
Author: jsalts
Date: 2018/06/29
Motivation
Makes import_playbook more useful.
Problems
What problems exist that this proposal will solve?
Currently there is no way to define variables exclusively for a playbook. Group vars is undesirable because it can affect multiple playbooks and --extra-vars means you can't store the variable in the yaml if you want to. There is a clear use case for passing the same variable into multiple import-playbook calls.