You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Martin Harris (JIRA)" <ji...@apache.org> on 2017/04/12 13:42:42 UTC
[jira] [Created] (BROOKLYN-472) YAML anchors cause failure when
adding YAML blueprint to catalog
Martin Harris created BROOKLYN-472:
--------------------------------------
Summary: YAML anchors cause failure when adding YAML blueprint to catalog
Key: BROOKLYN-472
URL: https://issues.apache.org/jira/browse/BROOKLYN-472
Project: Brooklyn
Issue Type: Bug
Affects Versions: 0.11.0
Reporter: Martin Harris
Priority: Minor
Deploying the following using the blueprint composer *works*
```
anchors:
- &systemTools
type: org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
name: System Tools
brooklyn.config:
launch.command: "true"
checkRunning.command: "true"
stop.command: "true"
pre.install.command: "true"
post.launch.command: "true"
services: [*systemTools]
location: localhost
```
Deploying the following using the blueprint import *doesn't work*
```
anchors:
- &systemTools
type: org.apache.brooklyn.entity.software.base.VanillaSoftwareProcess
name: System Tools
brooklyn.config:
launch.command: "true"
checkRunning.command: "true"
stop.command: "true"
pre.install.command: "true"
post.launch.command: "true"
brooklyn.catalog:
id: foobar
version: 1.0.0
itemType: template
name: foobar
item:
services: [*systemTools]
```
It fails with the following error:
Updating existing catalog entries is forbidden: foobar:1.0.0. Use forceUpdate argument to override.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)