Description of problem: Version-Release number of selected component (if applicable): RHQ 4.8-master How reproducible:always Steps to Reproduce: 1.create an alert definition on any resource, define at least 1 condition and 1 notification 2.GET /alert/definitions.json or /alert/definitions.xml Actual results:"conditions" and "notifications" are empty Expected results: "conditions" and "notifications" must be rendered within a response body.
You can get notifications and conditions either in an individual call or by requesting only one definition. I am not sure the full details should automatically be returned as this may be a huge amount of information. I can imagine though, to pass a flag "full" to request the definitions including conditions and notifications.
I agree with potential amount of information, but as soon as we have paging when listing definitions, I don't see it as an issue. I was not accurate when defining steps to repro. conditions and notifications are not retrieved even when requesting a single alert definition using GET /alert/definition/<ID>.json
You need to pass full=true as query param to GET /alert/definition/123.json?full=true This flag is what I am thinking of for this BZ as well.
Ah .. I am sorry, I've completely overlooked it in API documentation. It actually now makes sense for me not to include conditions and notifications when GET /alert/definitions (a client listing all alert defs is not interested in those data), having full parameter in this case might prevent client doing X requests (in case he really needs 'all' definitions with all details) But I still don't see use case why it is for one alert definition full=false by default.
master e718326 GET /alert/definitions now supports a boolean flag full, that is false by default . If set to true, conditions and notifications are returned as well. GET /alert/definition/{id} also has this flag. This is now true by default
Bulk close of old bugs in VERIFIED state.