GitHub user aledsage opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/593
Fix delete location from catalog
- On REST api (LocationResource.delete), when location is deleted
then delete from catalog as well as from LocationRegistry.
(Otherwise on rebind it will come back again!)
- Adds LocationApi.delete(symbolicName, version);
Previously just had delete(id))
- Adds to CatalogApi:
- deletePolicy
- deleteLocation
- listLocations
- Change CatalogApi.listEntities return type to List<CatalogEntitySummary>
instead of List<CatalogItemSummary>
- Cleanup LocationApi: deprecated methods to do with definitions,
preferring CatalogApi usage.
- Adds CatalogLocationSummary and LocationConfigSummary
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/incubator-brooklyn
fix/deleteLocationFromCatalog
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/593.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #593
----
commit f114676fd22b78d11ce1affa5afdbd6804b76c77
Author: Aled Sage <[email protected]>
Date: 2015-04-02T20:07:04Z
Fix delete location from catalog
- On REST api (LocationResource.delete), when location is deleted
then delete from catalog as well as from LocationRegistry.
(Otherwise on rebind it will come back again!)
- Adds LocationApi.delete(symbolicName, version);
Previously just had delete(id))
- Adds to CatalogApi:
- deletePolicy
- deleteLocation
- listLocations
- Change CatalogApi.listEntities return type to List<CatalogEntitySummary>
instead of List<CatalogItemSummary>
- Cleanup LocationApi: deprecated methods to do with definitions,
preferring CatalogApi usage.
- Adds CatalogLocationSummary and LocationConfigSummary
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
