GitHub user ahgittin opened a pull request:
https://github.com/apache/brooklyn-server/pull/573
Do not runtime-inherit catalog item
fixes https://issues.apache.org/jira/browse/BROOKLYN-445 and failing tests
included here
means catalog BOMs should be written such that any entity/policy/etc which
wants to access resources in the bundle is defined as its own item
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahgittin/brooklyn-server
do-not-inherit-catalog-item-id
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/573.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 #573
----
commit d7cbaeed46d7fedf8e49df015baa812352060f45
Author: Alex Heneveld <[email protected]>
Date: 2017-02-28T12:43:14Z
add original failing test from @sjcorbett
for failure to set inherited config keys -
https://issues.apache.org/jira/browse/BROOKLYN-445
commit edaf05441ee46d05e4479a79aee055e6cbfe1237
Author: Alex Heneveld <[email protected]>
Date: 2017-02-28T12:44:17Z
add similar tests, including one failing, isolating the error
commit 9c38c94eeeb5a3de2a082f81546440980b1abb5c
Author: Alex Heneveld <[email protected]>
Date: 2017-02-28T12:55:24Z
apply the fix for previous failing tests and
https://issues.apache.org/jira/browse/BROOKLYN-445
do not use a context catalog item id. this is a significant change and
release notes should be updated,
but it doesn't seem to break any of our tests; presumably most catalog
items are already refactoring
so each item is declared as its own item.
----
---
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.
---
