This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 968487b6 fix yaml format errors for workflow steps
968487b6 is described below
commit 968487b6e270909ba71cd15aad589ed62f412fd6
Author: Alex Heneveld <[email protected]>
AuthorDate: Wed Nov 30 16:25:38 2022 +0000
fix yaml format errors for workflow steps
---
_build/build.sh | 2 +-
guide/blueprints/workflow/steps/steps.yaml | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/_build/build.sh b/_build/build.sh
index 889eab47..a51d9849 100755
--- a/_build/build.sh
+++ b/_build/build.sh
@@ -232,7 +232,7 @@ function make_jekyll() {
fi
fi
- echo JEKYLL running with: jekyll build $JEKYLL_CONFIG
+ echo JEKYLL running with: jekyll build --config $JEKYLL_CONFIG
jekyll build --config $JEKYLL_CONFIG || return 1
echo JEKYLL completed
diff --git a/guide/blueprints/workflow/steps/steps.yaml
b/guide/blueprints/workflow/steps/steps.yaml
index 6024610b..70abdfba 100644
--- a/guide/blueprints/workflow/steps/steps.yaml
+++ b/guide/blueprints/workflow/steps/steps.yaml
@@ -174,7 +174,7 @@
Runs nested workflow, optionally over an indicated target.
This step type is described in more detail
[here](../nested-workflow.md).
It can also
- shorthand: '`workflow [ replayable REPLAYBLE ] [ retention RETENTION ]`'
or custom
+ shorthand: '`workflow [ replayable REPLAYBLE ] [ retention RETENTION ]`
or custom'
input: |
* `steps`: a list of steps to run, run in a separate context
* `target`: an optional target specifier, an entity or input to the
steps for the sub-workflow,
@@ -372,7 +372,7 @@
* `type`: a registered type to deploy as a root application, without
any configuration; exactly one of this and `blueprint` is required
* `blueprint`: the blueprint to deploy
* `format`: optional format specifier for the blueprint
- output:
+ output: |
* `app`: the application instance deployed
- name: add-entity
@@ -382,7 +382,7 @@
* `type`: a registered type to add as a child here, without any
configuration; exactly one of this and `blueprint` is required
* `blueprint`: the blueprint of the entity, or a list of such
blueprints, to be added at the current entity
* `format`: optional format specifier for the blueprint
- output:
+ output: |
* `entities`: a list of entities added
* `entity`: if a single entity was added, that entity, otherwise unset
@@ -419,7 +419,7 @@
* `entity`: the entity or entity ID where the adjunct should be added,
defaulting to the current entity
* `unique-tag`: a tag to uniquely identify this adjunct, defaulting to
the workflow step; this will replace any instance with the same unique-tag at
the entity
(to make the operation idempotent)
- output:
+ output: |
* `adjunct`: the policy or other adjunct added
* `policy` or `enricher` or `feed`: as above, depending on the type of
the adjunct
