GitHub user ahgittin opened a pull request:
https://github.com/apache/brooklyn-server/pull/967
add an /applications/details endpoint which corrects problems with /fetch
and adds some new features:
noticed that fetch actually recurses through all children entities which
was never the intention and is wasteful at scale. also for usability it would
be nice to include tags and all/regex sensors and config values. this adds
support for that.
i've deprecated the existing `/fetch` call but left its behaviour
unchanged. have also expanded description of `/list` endpoint.
to make this easier i've promoted `getAll()` from SensorSupportInternal.
previously we had no way on the public API to list all sensors for an entity.
it is still @Beta.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahgittin/brooklyn-server
more-details-on-applications-endpoint
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/967.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 #967
----
commit db7f06df21f4f273ef349c9e62de206297c4387c
Author: Alex Heneveld <alex.heneveld@...>
Date: 2018-06-01T11:42:14Z
add an /applications/details endpoint which corrects problems with /fetch
and adds new features
noticed that fetch actually recurses through all children entities which
was never the intention and is wasteful at scale.
also for usability it would be nice to include tags and all/regex sensors
and config values. this adds support for that.
i've deprecated the existing `/fetch` call but left its behaviour
unchanged. have also expanded description of `/list` endpoint.
to make this easier i've promoted `getAll()` from SensorSupportInternal.
previously we had no way on the public API to list all sensors for an entity.
it is still @Beta.
----
---
