brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-136) "Add a new location" not persisted
Date Tue, 17 Mar 2015 16:10:44 GMT


ASF GitHub Bot commented on BROOKLYN-136:

GitHub user aledsage opened a pull request:

    BROOKLYN-136: persist dynamic locations

    See javadoc on `BasicLocationRegistry` for a description of how this all hangs together.

You can merge this pull request into a Git repository by running:

    $ git pull feature/BROOKLYN-136-persist-dynamicLocations

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #555
commit d38788771c5ed67d7ab8fbdf105995a252174932
Author: Aled Sage <>
Date:   2015-03-17T14:46:28Z

    Adds Yamls.getAt utility

commit 3f52957d21421357003f70f847778167e6652e1b
Author: Aled Sage <>
Date:   2015-03-17T14:46:57Z

    Persist dynamically added locations in catalog
    - Support CatalogItem of type location
    - Location items added to catalog automatically added to
    - LocationResource.create adds new location type to Catalog


> "Add a new location" not persisted
> ----------------------------------
>                 Key: BROOKLYN-136
>                 URL:
>             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

View raw message