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
The following commit(s) were added to refs/heads/master by this push:
new fbb155be docs for https://github.com/apache/brooklyn-server/pull/1357
fbb155be is described below
commit fbb155be8adcf4d40557655afd95aeb51b27bb0f
Author: Alex Heneveld <[email protected]>
AuthorDate: Wed Sep 7 11:46:25 2022 +0100
docs for https://github.com/apache/brooklyn-server/pull/1357
---
guide/blueprints/catalog/schema.md | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/guide/blueprints/catalog/schema.md
b/guide/blueprints/catalog/schema.md
index 272c57ac..1dcc6a8e 100644
--- a/guide/blueprints/catalog/schema.md
+++ b/guide/blueprints/catalog/schema.md
@@ -107,10 +107,13 @@ Extensions may provide additional formats.
Exactly **one** of `item` and `items` is also required:
**`item`**
-The YAML for an entity, or policy, or location specification
-(a map containing `type` and optional `brooklyn.config`). For a "template"
item, it
+The YAML definition for a type such as an entity, policy, or location,
+such as a map containing `type` and optional `brooklyn.config`. For a
"template" item, it
should be a map containing `services` (i.e. the usual YAML format for a full
application
blueprint).
+This value may also be a URL e.g. `classpath://other-blueprint.yaml` to
indicate that the
+referenced URL should be read to supply the item, which is useful if the
blueprint exists
+as a standalone file, such as one developed in the composer.
**`items`**
A list of catalog items, where each entry in the map follows the same schema as
