GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/160
Test and fix locations not being unmanaged [updated #148]
This PR replaces https://github.com/apache/brooklyn-server/pull/148
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server
fix/unmanage-locations-aled
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/160.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 #160
----
commit 4070cbdccb5560b8f494b93e829551b3da8c34e5
Author: Svetoslav Neykov <[email protected]>
Date: 2016-05-20T15:11:41Z
Test and fix locations not being unmanaged
Only MachineLocation locations created by SoftwareProcess are unmanaged.
Currently there's no owner for LocationResolver locations so there's no one to
unmanage them.
The changes will mark locations created as part of bringing up a spec as
owner by the entity where they are attached. When the entity is unmanaged the
locations will be unmanaged as well.
commit 73895e5eaa9ed3d07ee540e541d3f8b4ed3cab5f
Author: Aled Sage <[email protected]>
Date: 2016-05-27T14:47:32Z
PR #148: auto-unmanaged locations incorporate comments
----
---
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.
---
