bb8cb15d20
Currently, multiple scripts are being stored in /var/lib/container-config-scripts directory if any of theses scripts are being used during the update_tasks the content won't be up to date (or the script will be fully missing if added in a new release), as the content of this folder is being updated during the deploy tasks (step 1), which occurs after all the update_tasks. This patch gathers the tasks responsible for the folder creation and content update into a new playbook named common_container_config_scripts.yaml, this way we can reference the tasks from the deploy-tasks step1 playbook (as it was happening up to now) and invoke them before the update_tasks playbook gets called. Change-Id: I2ac6bb98e1d4183327e888240fc8d5a70e0d6fcb Related-Bug: #1904193 |
||
|---|---|---|
| .. | ||
| services | ||
| common-container-config-scripts.yaml | ||
| container-puppet.sh | ||
| deploy-steps-playbooks-common.yaml | ||
| deploy-steps-tasks-step-0.j2.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 | ||