You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@brooklyn.apache.org by iu...@apache.org on 2022/06/27 15:52:55 UTC
[brooklyn-docs] branch master updated (45106b49 -> dcf71546)
This is an automated email from the ASF dual-hosted git repository.
iuliana pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
from 45106b49 Merge branch 'master' into effector-hints
new bedfd731 fix/dsl-mention
new db40cbd5 Merge branch 'master' of github.com:apache/brooklyn-docs
new dcf71546 Fixed formatting errors
The 3 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/yaml-reference.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
[brooklyn-docs] 01/03: fix/dsl-mention
Posted by iu...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
iuliana pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit bedfd73166cb48e27575df2973929ccc47098653
Author: iuliana <iu...@cloudsoft.io>
AuthorDate: Wed May 11 14:05:06 2022 +0100
fix/dsl-mention
---
guide/blueprints/yaml-reference.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/guide/blueprints/yaml-reference.md b/guide/blueprints/yaml-reference.md
index ca4995a0..72a3e175 100644
--- a/guide/blueprints/yaml-reference.md
+++ b/guide/blueprints/yaml-reference.md
@@ -263,8 +263,9 @@ concise DSL defined here:
<!-- TODO examples for object and entitySpec -->
-Parameters above can be supplied either as strings or as lists and maps in YAML,
-and the `$brooklyn:` syntax can be used within those parameters.
+Parameters above can be supplied either as strings or as lists and maps in YAML, and the `$brooklyn:` syntax can be used within those parameters.
+
+**Note:** The DSL is always supported for the values of config keys on entities. The DSL is supported in many other places also, but not all, depending on how the value is used there. For instance some aspects of a location or initializer may need to be retrieved without an entity context and so do not support DSL.
## Some Powerful YAML Entities
[brooklyn-docs] 02/03: Merge branch 'master' of github.com:apache/brooklyn-docs
Posted by iu...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
iuliana pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit db40cbd55e4018059332f68cf997a745023b5e84
Merge: bedfd731 45106b49
Author: iuliana <iu...@cloudsoft.io>
AuthorDate: Mon Jun 27 16:46:32 2022 +0100
Merge branch 'master' of github.com:apache/brooklyn-docs
_plugins/jekyll_relative_links.rb | 2 +-
guide/blueprints/yaml-reference.md | 154 ++++++++++++++++++++-
...ur.md => _stop-start-restart-behaviour.camp.md} | 15 +-
.../concepts/_stop-start-restart-bevaviour.camp.md | 3 -
guide/concepts/stop-start-restart-behaviour.md | 55 +-------
guide/ops/cli/cli-ref-guide.md | 11 +-
guide/ops/gui/blueprints.md | 2 +-
guide/ops/gui/managing.md | 2 +-
guide/ops/logging/logbook.md | 4 +-
9 files changed, 165 insertions(+), 83 deletions(-)
[brooklyn-docs] 03/03: Fixed formatting errors
Posted by iu...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
iuliana pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
commit dcf7154603074a4fca463ca9acbba7f44f185e64
Author: iuliana <iu...@cloudsoft.io>
AuthorDate: Mon Jun 27 16:52:41 2022 +0100
Fixed formatting errors
---
guide/blueprints/yaml-reference.md | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/guide/blueprints/yaml-reference.md b/guide/blueprints/yaml-reference.md
index 3fc0e88a..3af50824 100644
--- a/guide/blueprints/yaml-reference.md
+++ b/guide/blueprints/yaml-reference.md
@@ -253,7 +253,7 @@ concise DSL defined here:
* `$brooklyn:urlEncode("val")` returns a future which creates a string with the characters escaped
so it is a valid part of a URL. The parameter can be a string *or* another task. For example,
`$brooklyn:urlEncode($brooklyn:config(\"mykey\"))`. It uses "www-form-urlencoded" for the encoding,
- which is appropriate for query parameters but not for some other parts of the URL (e.g. space is encoded as '+').
+ which is appropriate for query parameters but not for some other parts of the URL (e.g. space is encoded as `'+'`).
* `$brooklyn:literal("string")` returns the given string as a literal (suppressing any `$brooklyn:` expansion)
* `$brooklyn:object(Map)` creates an object, using keys `type` to define the java type,
and either `object.fields` or `brooklyn.config` to supply bean/constructor/flags to create an instance
@@ -362,7 +362,7 @@ and false otherwise. The full set of individual tests are:
and otherwise it will return false
* `greater-than: <object>`, as above
* `less-than-or-equal-to: <object>` as above
-* `greater-than-or-equal-to: <object>, as above
+* `greater-than-or-equal-to: <object>`, as above
* `in-range: <range>`, where `<range>` is a list of two numbers, e.g. `[0,100]` (always inclusive)
* `java-instance-of: <string>`, where the `<string>` is a registered type name, to test
type assignment of the underlying java class of the value being tested with the
@@ -373,8 +373,8 @@ and false otherwise. The full set of individual tests are:
Two composite tests are supported, both taking a list of other `<test>` objects
(as a list of YAML maps):
-* `any: <list of tests>`, testing that any of the tests in the list are true (logical "or")
-* `all: <list of tests>`, testing that all of the tests in the list are true (logical "and")
+* `any: <list of tests>`, testing that any of the tests in the list are true (logical `"or"`)
+* `all: <list of tests>`, testing that all of the tests in the list are true (logical `"and"`)
@@ -406,9 +406,9 @@ the `DslPredicate` via `DslEntityPredicate`:
or a keyword, currently `location` or `children`, to evaluate
against the location(s) or children of that entity
* `config: <string>`: indicates that the tests should be applied to the value of config key
- `<string> on the context entity, location, or policy
+ `<string>` on the context entity, location, or policy
* `sensor: <string>`: indicates that the tests should be applied to the value of sensor
- `<string> on the context entity
+ `<string>` on the context entity
* `tag: <test>`: indicates that `<test>` should be applied to the tags on the context entity, location, or policy