You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@brooklyn.apache.org by he...@apache.org on 2023/12/07 12:53:52 UTC
(brooklyn-docs) branch master updated (44e75be1 -> 9fde234b)
This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
from 44e75be1 Merge pull request #381 from iuliana/link-fix
new 7466d93a better docs for update-children step
new 9fde234b tidy some links in workflow
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
guide/blueprints/workflow/common.md | 2 +-
guide/blueprints/workflow/steps/index.md | 8 ++++----
guide/blueprints/workflow/steps/steps.yaml | 9 +++++----
3 files changed, 10 insertions(+), 9 deletions(-)
(brooklyn-docs) 02/02: tidy some links in workflow
Posted by he...@apache.org.
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 9fde234b397accea79297fb110b29ed404aa4412
Author: Alex Heneveld <al...@cloudsoft.io>
AuthorDate: Thu Dec 7 12:53:37 2023 +0000
tidy some links in workflow
---
guide/blueprints/workflow/common.md | 2 +-
guide/blueprints/workflow/steps/index.md | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/guide/blueprints/workflow/common.md b/guide/blueprints/workflow/common.md
index f18d7f32..910a5324 100644
--- a/guide/blueprints/workflow/common.md
+++ b/guide/blueprints/workflow/common.md
@@ -81,7 +81,7 @@ steps:
### Conditions
The previous example shows the use of conditions, as mentioned as one of the properties common to all steps.
-This makes use of the recent "[Predicate DSL](https://github.com/apache/brooklyn-docs/blob/master/guide/blueprints/yaml-reference.md#predicate-dsl)" conditions framework .
+This makes use of the recent "[Predicate DSL](../yaml-reference.md#predicate-dsl)" conditions framework .
It is normally necessary to supply a `target`, unless one of the entity-specific target keys (e.g. `sensor` or `config`)
is used. The target and arguments here can use the [workflow expression syntax](variables.md).
diff --git a/guide/blueprints/workflow/steps/index.md b/guide/blueprints/workflow/steps/index.md
index 073c265e..ec9c71fd 100644
--- a/guide/blueprints/workflow/steps/index.md
+++ b/guide/blueprints/workflow/steps/index.md
@@ -13,13 +13,13 @@ Apache Brooklyn workflow supports a range of step types covering the most common
commonly done as part of application management.
These are divided into the following groups:
-* [Workflow Control](#workflow_control): use local variables and control flow,
+* [Workflow Control](#workflow-control): use local variables and control flow,
with step types such as `let`, `return`, and `retry`
-* [External Actions](#external_actions): interact with external systems
+* [External Actions](#external-actions): interact with external systems
using step types such as `container`, `ssh`, `winrm`, and `http`
-* [Application Models](#application_models): work with the models stored in Brooklyn,
+* [Application Models](#application-models): work with the models stored in Brooklyn,
doing things such as `invoke-effector`, `set-sensor`, `deploy-application`, and `add-entity`
-* [General Purpose](#general_purpose): miscellaneous step types such as `log` and `sleep`
+* [General Purpose](#general-purpose): miscellaneous step types such as `log` and `sleep`
Custom step types can be written and added to the catalog, either written as workflow using these primitives
(including doing virtually anything in a container) or by implementing a Java type, both [as described here](../nested-workflow.md).
(brooklyn-docs) 01/02: better docs for update-children step
Posted by he...@apache.org.
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 7466d93abb64e1a727f4be6b26959c008c2a6175
Author: Alex Heneveld <al...@cloudsoft.io>
AuthorDate: Thu Dec 7 12:49:37 2023 +0000
better docs for update-children step
---
guide/blueprints/workflow/steps/steps.yaml | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/guide/blueprints/workflow/steps/steps.yaml b/guide/blueprints/workflow/steps/steps.yaml
index e84fba15..50bed277 100644
--- a/guide/blueprints/workflow/steps/steps.yaml
+++ b/guide/blueprints/workflow/steps/steps.yaml
@@ -529,10 +529,11 @@
the default behavior is to invoke an `on_create` effector at the child (if there is such an effector, otherwise do nothing), passing `item`;
this is invoked prior to `on_update` so if there is nothing special needed for creation this can be omitted
- * `on_update`: a workflow to run on each child which has a corresponding item,
- passed the `item` (and all inputs to the `update-children` step),
- and typically updating config and sensors as appropriate on the child;
- the default behavior is to invoke an `on_update` effector at the child (if there is such an effector, otherwise do nothing), passing `item`;
+ * `on_update`: a workflow to run for each child which has a corresponding item,
+ run in the context of the parent, passed the `child` and `item` and `index`
+ (and all inputs to the `update-children` step),
+ and typically updating config and sensors as appropriate on the child, possibly in a sub-workflow in `target: child`;
+ the default behavior is to invoke an `on_update` effector at the child (if there is such an effector, otherwise do nothing);
if the name or any policies may need to change on update, that should be considered in this workflow;
if the `update-children` is performed frequently, it might be efficient in this method to check whether the `item` has changed