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

commit 9be2adfa7966b1fe0e9c48b7cf11df9491533cce
Author: Alex Heneveld <a...@cloudsoft.io>
AuthorDate: Fri May 19 16:56:14 2023 +0100

    document allowing list of steps as a custom workflow
---
 guide/blueprints/workflow/nested-workflow.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/guide/blueprints/workflow/nested-workflow.md 
b/guide/blueprints/workflow/nested-workflow.md
index e5c68bcd..7a09c08c 100644
--- a/guide/blueprints/workflow/nested-workflow.md
+++ b/guide/blueprints/workflow/nested-workflow.md
@@ -115,6 +115,11 @@ It also accepts the standard step keys such as `input`, 
`timeout` on `on-error`.
 A user of the defined step type can also supply `output` which, as per other 
steps,
 is evaluated in the context of the outer workflow, with visibility of the 
output from the current step.
 
+When supplying a workflow in contexts where a `workflow` is already expected,
+such as in a config key that takes a `workflow` (a Java `CustomWorkflowStep`),
+it is not necessary to specify the `type: workflow`, and additionally, if the 
only things being set is `steps`, those steps can be provided as a list without 
the `steps` keyword.
+Internally a _list_ will coerce to a `workflow` by interpreting the list as 
the steps.
+
 
 #### Shorthand Template Syntax
 

Reply via email to