Merge "Sphinx throws warnings on workbooks descriptions"
This commit is contained in:
commit
5985d39f8b
|
@ -17,15 +17,15 @@ workflows:
|
|||
calling workflow.
|
||||
|
||||
If plan_name is provided the message will be persisted to Swift. In a
|
||||
container named "{plan_name}-messages". The swift objects will be
|
||||
named:
|
||||
container named "{plan_name}-messages". The swift objects will be named:
|
||||
|
||||
{TYPE}/{TIMESTAMP}.yaml
|
||||
|
||||
If a deployment_status is provided, the top-level deployment_status.yaml
|
||||
will also be updated, which will contain the deployment_status and the
|
||||
related message.
|
||||
|
||||
The standard message format will be:
|
||||
The standard message format will be::
|
||||
|
||||
body: {
|
||||
type: 'tripleo.workflow.name', # Matches the workflow name
|
||||
|
|
|
@ -50,7 +50,7 @@ workflows:
|
|||
|
||||
object_exists:
|
||||
|
||||
description: >-
|
||||
description: >
|
||||
Verify if a Swift object exists
|
||||
|
||||
Given the name of a Swift container and object this workflow will
|
||||
|
|
Loading…
Reference in New Issue