Add playbooks
to specify multiple playbooks to run
#54
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.
Adds
playbooks
config.Why
When running "complex" playbook provisioning scenarios before testing, you may need to re-use different playbooks.
For example I was testing playbooks.
However for the release process provisioning from scratch you execute e.g playbook
db.yml
andweb.yml
.They're separate and if I was to create a new playbook that includes both roles used, I wouldn't test the actual playbooks executed.
So with this change usage is
Anything other than an
Array
will be marked as invalid configuration. E.gImportant
Includes #51
@ahelal