GitHub user tbouron opened a pull request:
https://github.com/apache/brooklyn-server/pull/638
Add support for managing enrichers within the catalog
This allows enrichers to be registered within the Brooklyn catalog, same as
entities or policies. It allows enrichers' registration via:
- `@Catalog` annotation on the java class
- YAML with an `itemType: enricher`
This also adds 3 endpoints to the `/v1/catalog` REST API:
- `GET /v1/catalog/enrichers` returns the list of all registered enrichers
- `GET /v1/catalog/enrichers/<enricherId>/<version>` returns the detail of
a specific enricher
- `DELETE /v1/catalog/enrichers/<enricherId>/<version>` details a specific
enricher
_PS: If the PR is too big, I can split up to multiples PRs. Hopefully the
commit's messages are pretty clear_
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tbouron/brooklyn-server
feature/catalog-enrichers
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/638.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 #638
----
commit 26c72b97773942bcdde64eb829cf860f7c3d43ce
Author: Thomas Bouron <thomas.bou...@cloudsoftcorp.com>
Date: 2017-04-14T19:07:35Z
Add support for managing enrichers within the catalog (automatically
scanned and YAML parsed, same as entities or policies)
commit 17ef9ed360872a78c6d8b9094558ce9aa49b362f
Author: Thomas Bouron <thomas.bou...@cloudsoftcorp.com>
Date: 2017-04-14T19:08:20Z
Add @Catalog annotation to existing enrichers
commit 92ee24e5844e74975034a5f94bedd642d6012a3b
Author: Thomas Bouron <thomas.bou...@cloudsoftcorp.com>
Date: 2017-04-14T19:09:16Z
Add support for enrichers catalog items on the REST API (CRUD)
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
