So this should have a do not merge tag on it?

@Jiri-Kremser do you plan on making those changes needed?

So this should have a do not merge tag on it?

right, well, it's always kind of chicken-egg problem here, what should go first? The backend change, the ui-services that depends on this backend api? or the hawkular/hawkular ui code that uses the ui-services, but at the same time increases the version of the component with the backend change.

Obviously the backend change can go first, because it doesn't depend on the UI (nor ui-services), but it's not so clear with the hawkular/hawkular and hawkular/ui-services, in ideal world the 2 PRs should be merged in the same moment. Or firstly, release the new version of the ui-services and let the hawkular ui still depend on the latest-1 version.

so it can be merged provided the hawkular ui will not depend on it immediately

do you plan on making those changes needed?

yes, I can do that (tomorrow perhaps)

@vrockai could you please review?

@Jiri-Kremser , I just went through the code and it seems fine. Just two tiny remarks:

• Please don't add dist files to the commit. The dist is generated before release and it's part of the release commit.
• Could you please add rest-tests for new entities?

Please don't add dist files to the commit. The dist is generated before release and it's part of the release commit.

• checked

Could you please add rest-tests for new entities?

• checked

rebased against latest master and ready to merge (this PR should go right after this one hawkular/hawkular-dist-old#434)

Merged #28