Bug 975526

Summary:	Improve validation of alert conditions for different resource types
Product:	[Other] RHQ Project	Reporter:	Libor Zoubek <lzoubek>
Component:	REST	Assignee:	Heiko W. Rupp <hrupp>
Status:	NEW ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.8	CC:	theute
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Libor Zoubek 2013-06-18 17:08:18 UTC

Description of problem: Currently, REST api allows to create alert conditions, that are not allowed in UI.


Version-Release number of selected component (if applicable):
RHQ 4.8-master

How reproducible: always


For example: 
1. You can create a condition of RESOURCE_CONFIG category for resource that does not support configuration
2. You can create a condition of AVAILABILITY with various availability options for platform resource (where some options are not allowed)
3. You can create a condition of DRIFT type for resource without drift support

REST API Should check for these "special" conditions.