Skip to content
Permalink
Browse files
Merge branch 'master' of github.com:apache/brooklyn-docs
  • Loading branch information
nakomis committed Feb 5, 2019
2 parents d616fbf + 8d7b942 commit a7dbdc2a0908cb3f40520ebb5c2a5a99389701e7
Showing 3 changed files with 15 additions and 7 deletions.
@@ -58,13 +58,19 @@ and for a complete reference on the syntax of `brooklyn.parameters` see that sec

#### Config Key Constraints

The config keys in the `brooklyn.parameters` can also have constraints defined, for what values
The config keys in the `brooklyn.parameters` can also have a list of constraints defined, for what values
are valid. If more than one constraint is defined, then they must all be satisfied. The constraints
can be any of:

* `required`: deployment will fail if no value is supplied for this config key.
* `regex: ...`: the value will be compared against the given regular expression.
* A predicate, declared using the DSL `$brooklyn:object`.
* `required`: deployment will fail if no value is supplied for this config key
* `regex: <pattern>`: the value must match the regular expression `<pattern>`
* `glob: <pattern>`: the value must match the bash-style wildcard glob `<pattern>`
* `urlExists: <url>`: the server must be able to resolve and access the URL `<url>`
* `forbiddenIf: <key>`: setting a value is disallowed if the config key `<key>` has a value set
* `forbiddenUnless: <key>`: setting a value is disallowed if the config key `<key>` does not have a value set
* `requiredIf: <key>`: a value is required if the config key `<key>` has a value set
* `requiredUnless: <key>`: a value is required if the config key `<key>` does not have a value set
* Any java `Predicate`, declared using the DSL `$brooklyn:object`.

This is illustrated in the example below:

@@ -128,8 +128,10 @@ there are a few options for getting an equivalent OSGi bundle:

* Use the `wrap:` prefix. The [PAX URL Wrap protocol](https://ops4j1.jira.com/wiki/display/paxurl/Wrap+Protocol)
is an OSGi URL handler that can process your legacy jar at runtime and transform it into an OSGi bundle.
This can be used when declaring a dependency in your feature.xml, and when using the Karaf console's
`bundle:install`. Note that it is not yet supported in Brooklyn's `brooklyn.libraries` catalog items.
This can be used when declaring a dependency in your feature.xml, and when using the Karaf console's
`bundle:install`. Note that it is not yet supported in Brooklyn's `brooklyn.libraries` catalog items.
When using `wrap:` include the `Bundle-SymbolicName` and `Bundle-Version` headers as parameters. (e.g.
`wrap:mvn:javax.xml.ws/jaxws-api/2.3.0$Bundle-Symbolic-Name=javax.xml.ws.api&amp;Bundle-Version=2.3.0`)

* Re-package the bundle yourself, offline, to produce a valid OSGi bundle.

@@ -130,4 +130,4 @@ you can monitor the progress of the application deployment and verify if it was

Having deployed an application, the next step is **[monitoring and managing](managing.html)** it.

</div>
</div>

0 comments on commit a7dbdc2

Please sign in to comment.