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 ad6de9c section on what is editable in catalog
ad6de9c is described below
commit ad6de9c823e3d968d6b242d9885b220bef698b5e
Author: Alex Heneveld <[email protected]>
AuthorDate: Wed Jun 23 09:51:58 2021 +0100
section on what is editable in catalog
---
guide/blueprints/catalog/templates.md | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/guide/blueprints/catalog/templates.md
b/guide/blueprints/catalog/templates.md
index 06212d9..84c102b 100644
--- a/guide/blueprints/catalog/templates.md
+++ b/guide/blueprints/catalog/templates.md
@@ -77,3 +77,13 @@ brooklyn.catalog:
[](quick-launch-template.png)
+
+### Editing from Catalog and from Templates
+
+Only bundles created by uploading to the catalog a single BOM fle containing a
single entity -- eg `br catalog add my.bom` or added from the Composer -- are
able to be edited directly from the Catalog. When a ZIP/JAR/directory is
uploaded to the catalog, the type it contains are not editable via the UI.
This is because the UI does not support editing multiple files and a folder
structure, and to prevent confusion where items from a multi-type bundle (an
archive, eg `br catalog add my.z [...]
+
+It is of course possible to copy the source code of a type to the composer
(from a source control project or from the Catalog), edit it in the composer,
edit it in your source control project, and then create and upload a new bundle.
+
+It is supported standard practice for items labeled as "templates", to be
opened in the Composer via the Quick Launch, edited, and saved back as a new
item (new name and bundle); this is creating a new type from an existing
template, rather than attempting to update the template in situ, so does not
expose users to the confusion of the same type in multiple bundles.
+
+
