brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Heneveld (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-136) "Add a new location" not persisted
Date Wed, 11 Mar 2015 09:25:38 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356521#comment-14356521
] 

Alex Heneveld commented on BROOKLYN-136:
----------------------------------------

makes sense to me, and i don't think it should be too hard

having locations come from catalog might clean up the current definition/registry mess

if we treat brooklyn.properties as a pure override, clobbering anything in catalog, that should
be good enough.  in future we could deprecate brooklyn.properties as a source of locations.

> "Add a new location" not persisted
> ----------------------------------
>
>                 Key: BROOKLYN-136
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-136
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.7.0-SNAPSHOT
>            Reporter: Aled Sage
>
> If I use the web-console's Catalog tab, and click the "+" to add a new location... The
location is successfully added and is usable (i.e. it appears in the drop-down list of available
locations when adding an application, or can be referenced in YAML).
> However, when I restart Brooklyn the location has disappeared.
> It should be persisted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message