Github user Graeme-Miller commented on a diff in the pull request:
https://github.com/apache/incubator-brooklyn/pull/1107#discussion_r47520858
--- Diff: docs/guide/yaml/advanced-example.md ---
@@ -74,10 +77,10 @@ customize.command: |
$brooklyn:config("elasticsearch.tcp.port")
)
~~~
-The purpose of this section is to create a YAML file with all of the
required configuration. We use the YAML literal style "|" indicator to write a
multi line command. We then use $brooklyn:formatString notation to build the
string from configuration. We start our series of commands by using the "rm"
command to remove the previous config file. We then use "echo" and "tee" to
create the new config file and insert the config. Part of the configuration is
a list of all hosts that is set on the parent entity- this is done by using a
combination of the "component" and "attributeWhenReady" DSL commands. More on
how this is generated later.
+The purpose of this section is to create a YAML file with all of the
required configuration. We use the YAML literal style `|` indicator to write a
multi line command. We then use `$brooklyn:formatString` notation to build the
string from configuration. We start our series of commands by using the `rm`
command to remove the previous config file. We then use `echo` and `tee` to
create the new config file and insert the config. Part of the configuration is
a list of all hosts that is set on the parent entity- this is done by using a
combination of the `component` and `attributeWhenReady` DSL commands. More on
how this is generated later.
##### Check running
-After an app is installed and run, this command will be run regularly and
used to populate the "service.isUp" sensor. If this command is not specified,
or returns an exit code of anything other than zero, then Brooklyn will assume
that your entity is broken and will display the fire status symbol. Please
refer to the following section of the Elasticsearch blueprint:
+After an app is installed and run, this command is scheduled to run
regularly and used to populate the `service.isUp` sensor. If this command is
not specified, or returns an exit code of anything other than zero, then
Brooklyn will assume that your entity is has failed and will display the fire
status symbol. Please refer to the following section of the Elasticsearch
blueprint:
--- End diff --
'is has failed',
should be 'is broken' or 'has failed'
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
