From 71f13388161cbab12fe284f7b251ca8d36f7635c Mon Sep 17 00:00:00 2001 From: Giulio Fidente Date: Sat, 6 May 2017 02:19:47 +0200 Subject: Allows use of Mistral workflows during deployment steps Introduces a general mechanism meant to allow for the execution of workflows during the deployment steps. Services can define workflow actions to be triggered during a step in the newly added service_workflow_tasks section. The syntax is: service_workflow_tasks: step2: - name: my_action_name action: std.echo input: output: 'hello world' Implements: blueprint tripleo-ceph-ansible Depends-On: If02799e7457ca017cc119317dfb2db7198a3559f Depends-On: Ibc5707f9f06266fe84ad1dd91dcb984157871d30 Change-Id: I36a642fbc2076ad9e4a10ffc56d6d16f3ed6f27a --- puppet/post.j2.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'puppet/post.j2.yaml') diff --git a/puppet/post.j2.yaml b/puppet/post.j2.yaml index 3a15cec6..370ffa8a 100644 --- a/puppet/post.j2.yaml +++ b/puppet/post.j2.yaml @@ -8,7 +8,9 @@ parameters: servers: type: json description: Mapping of Role name e.g Controller to a list of servers - + stack_name: + type: string + description: Name of the topmost stack role_data: type: json description: Mapping of Role name e.g Controller to the per-role data @@ -24,5 +26,4 @@ parameters: Setting this to a unique value will re-run any deployment tasks which perform configuration on a Heat stack-update. -resources: {% include 'puppet-steps.j2' %} -- cgit 1.2.3-korg