GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/730
Use enricher spec instead of constructor
Changes (mostly test) code to use `EnricherSpec` to create enrichers,
rather than calling the enricher's constructor. As for
https://github.com/apache/brooklyn-server/pull/729, there are two big reasons
for doing this:
1. the `EnricherSpec` approach is the same as is used by yaml blueprints -
by using/testing in this way, we are more confident that we'll be able to do
the same in yaml blueprints.
2. we want to simplify our code - reducing the number of ways a
policy/enricher/location/entity can be created and configured will give us some
simplification.
This PR also deletes some deprecated enrichers. They were not written in a
way that was compatible with persisted state, so I believe we won't impact any
users who have these persisted.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server
use-EnricherSpec-instead-of-constructor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/730.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 #730
----
----
---
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.
---
