Browse Source

Move deploy-steps-playbook to deploy-steps-tasks

So that we can more easily iterate over an include in an output

Change-Id: Idd5bb47589e5c37123caafcded1afbff8881aa33
changes/86/485686/12
Steven Hardy 4 years ago
committed by Emilien Macchi
parent
commit
76421eb249
  1. 6
      common/deploy-steps-tasks.yaml
  2. 10
      common/deploy-steps.j2

6
common/deploy-steps-playbook.yaml → common/deploy-steps-tasks.yaml

@ -1,6 +1,6 @@
- hosts: localhost
connection: local
tasks:
# Note the indentation here is required as it's joined
# to create a playbook in deploy-steps.j2
#####################################################
# Per step puppet configuration of the baremetal host
#####################################################

10
common/deploy-steps.j2

@ -72,7 +72,15 @@ resources:
- name: update_identifier
- name: bootstrap_server_id
- name: docker_puppet_debug
config: {get_file: deploy-steps-playbook.yaml}
config:
str_replace:
template: |
- hosts: localhost
connection: local
tasks:
_TASKS
params:
_TASKS: {get_file: deploy-steps-tasks.yaml}
{%- for step in range(1, deploy_steps_max) %}
# BEGIN service_workflow_tasks handling

Loading…
Cancel
Save