Please sign in to comment.
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
- Loading branch information...
Showing with 183 additions and 13 deletions.
|@@ -0,0 +1,8 @@|
|It is now possible to trigger Mistral workflows or workflow actions|
|before a deployment step is applied. This can be defined within the|
|scope of a service template and is described as a task property|
|for the Heat OS::Mistral::Workflow resource, for more details also|
|see the puppet/services/README.rst file.|