[
https://issues.apache.org/jira/browse/BROOKLYN-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228216#comment-15228216
]
Aled Sage commented on BROOKLYN-248:
------------------------------------
For the short/medium term fix, I've put in location-specific behaviour to fix
this issue. I've added more thorough test cases, marking two as "WIP" in
{{ApplicationYamlTest}}.
The behaviour shown in {{CatalogYamlLocationTest.testNamePrecedence()}} also
needs further thought and attention. Do we just tell people to not define the
name in multiple places (which would seem reasonable)? Or do we try to support
this so that it always respects the most specific value (which is what happens
for entities currently)?
> Incorrect name in derived locations
> -----------------------------------
>
> Key: BROOKLYN-248
> URL: https://issues.apache.org/jira/browse/BROOKLYN-248
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.9.0
> Environment: OSX
> Reporter: Duncan Godwin
>
> The following location displays "Test Location 1" for both "Test Location 1"
> and "Test Location 2" when you use it to launch an application.
> See the screenshot here:
> https://s3.amazonaws.com/drigodwin-misc/brooklyn-248-ss.png
> {code}
> brooklyn.catalog:
> version: 0.2.0
> items:
> - id: test-location-1
> name: "Test Location 1"
> itemType: location
> item:
> type: byon:(hosts="10.10.10.102")
> brooklyn.config:
> displayName: testingdisplayName
> user: testinguser
> password: testingpassword
> privateKeyFile: testingprivateKeyFile
> privateKeyPassphrase: testingprivateKeyPassphrase
> - id: test-location-2
> name: "Test Location 2"
> itemType: location
> item:
> type: test-location-1
> brooklyn.config:
> displayName: testingdisplayName2
> user: testinguser2
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
