marios 0c76a2acbf Start step at 0 for update_ + upgrade_steps_playbook ... In I93dc8b4cefbd729ba7afa3a4d81b4ac95344cac2 for bug 1717292 the step variable passed into the update_steps_playbook and the upgrade_steps_playbook outputs is set to start at sequence 1. This means that any upgrade or update_tasks that are expected to run in step 0 will never be executed. Change-Id: Ic2dab617269d47c4ea028cb35cdba2068a467ff9 Closes-Bug: 1741926		2018-01-08 16:31:40 +00:00
..
deploy-steps-tasks.yaml	puppet apply: add --summarize	2018-01-04 09:37:46 -08:00
deploy-steps.j2	Start step at 0 for update_ + upgrade_steps_playbook	2018-01-08 16:31:40 +00:00
major_upgrade_steps.j2.yaml	Merge "Add name property where missing"	2017-12-05 18:07:49 +00:00
post-upgrade.j2.yaml	Add RoleConfig output to major_upgrade_steps.j2.yaml	2017-09-12 09:58:50 +01:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00
services.yaml	Add deploy_steps_tasks interface	2017-12-05 08:47:48 +02:00