c8fba9b237
These role task inclusions force a linear-like sequence and result in a lot of unnecessary skipped tasks. This takes extra time, and causes a lot of log noise which makes debugging more difficult. Given that a host can ever only have a single role, it makes more sense to just include the applicable role task file if it exists. Change-Id: Id2cadceaaf563dc94fcf2d8ce0f0cb9054a65d40 |
||
---|---|---|
.. | ||
services | ||
common-container-config-scripts.yaml | ||
common-container-setup-tasks.yaml | ||
container-puppet.sh | ||
deploy-steps-playbooks-common.yaml | ||
deploy-steps-tasks-step-0.yaml | ||
deploy-steps-tasks-step-1.yaml | ||
deploy-steps-tasks.yaml | ||
deploy-steps.j2 | ||
generate-config-tasks.yaml | ||
hiera-steps-tasks.yaml | ||
host-container-puppet-tasks.yaml | ||
post.j2.yaml |