Emilien Macchi 0bc3e99016 Honor --skip-deploy-identifier in common deploy tasks for updates ... To continue the work that was done in I711dbb00a9c34dbd96ef179ef41bff281b0001d1, we also need to skip the common deploy tasks if --skip-deploy-identifier is passed by the operator. When using --skip-deploy-identifier, the UpdateIdentifier is set to None. Ansible doesn't see None as "", so we really need to test if the variable is defined or not. That patches changes the logic to test that. We also support the case where the variable is set to "", and consider is as empty which means we want to skip the deploy/updates. It is also doing it for the update playbooks which includes tasks from commont deploy. It is not replicating the exact condition as in deploy_steps_playbook. There is no need to also check if /var/lib/docker-container-startup-configs.json file is here because it has been created during the initial deployment. This fix the bug where --skip-deploy-identifier wasn't honored during stack updates. Co-Authored-By: Thomas Hervé <therve@redhat.com> Co-Authored-By: Sam Doran <sdoran@redhat.com> Change-Id: Ibab17dcaeebea65135fca4f40562109c90f36c27 Related-Bug: #1796924 (cherry picked from commit 5ac6d19f58)		2018-11-19 14:25:41 +00:00
..
deploy-steps-tasks.yaml	check mode: paunch configs	2018-10-22 09:26:18 -04:00
deploy-steps.j2	Honor --skip-deploy-identifier in common deploy tasks for updates	2018-11-19 14:25:41 +00:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00
services.yaml	Update and upgrade tasks for services deployed via external deploy tasks	2018-08-02 15:04:15 +02:00