John McCabe created BROOKLYN-261:
------------------------------------
Summary: Unable to use previous catalog item in the same file if
nested inside services
Key: BROOKLYN-261
URL: https://issues.apache.org/jira/browse/BROOKLYN-261
Project: Brooklyn
Issue Type: Bug
Affects Versions: 0.10.0, 0.9.1
Reporter: John McCabe
Priority: Minor
Attempting to add a catalog with multiple items where an item defined in the
catalog is used by a later item nested inside {{services:}} currently fails:
bq. Could not resolve item 'built-from-test-entity'; 2 errors including:
Transformer for Brooklyn OASIS CAMP interpreter gave an error creating this
plan: Unable to match plan item:
Service[name=<null>,description=<null>,serviceType=test-entity,characteristics=[],customAttributes={}]
{code:title=Not Working|xml}
brooklyn.catalog:
version: 0.0.1
items:
- id: test-entity
name: Test Entity
item:
services:
- type: org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
- id: built-from-test-entity
name: Built From Test Entity
item:
services:
- type: test-entity
{code}
*Note* that {{test-entity}} above must not already exist in the catalog or else
the bom above would load.
Altering the {{built-from-test-entity}} to not use nested services allows the
catalog bom to be added:
{code}
- id: built-from-test-entity
name: Built From Test Entity
item:
type: test-entity
{code}
But this does not help for cases where the nesting is necessary, for example:
{code}
- id: built-from-test-entity
name: Built From Test Entity
item:
services:
- type: test-entity
- type: another-entity
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
