Description of problem: We don't expose any methods to create, update or delete dyna-groups which prevents the CLI to automate working with them. This is a glaring omission, IMHO. Version-Release number of selected component (if applicable): 4.4.0-SNAPSHOT
Lukas What is the level of effort here?
I believe the effort should not be significant - it should be a matter of choosing the methods from the local iface to be exposed in the remote interface, too, possibly slightly changing their signatures to be more "user friendly". There is a support for criteria queries on group definitions so even our standard querying approach is already in place.
Targeting for JON3.2
master http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=74dfd37db time: Wed Jan 30 17:08:46 2013 +0100 commit: 74dfd37db100de71128db47eb83962c686c8c925 author: Jirka Kremser - jkremser message: [Bug 880819 - RFE: expose GroupDefinitionManager remotely] Subset of methods defined in the local intercace has been exposed via the remote interaces and registered in the RhqManager. Moving status to MODIFIED.
master http://git.fedorahosted.org/cgit/rhq/rhq.git/diff/?id=281605c82 281605c82 53 seconds ago Jirka Kremser [Bug 880819 - RFE: expose GroupDefinitionManager remotely] No need for exposing the "getById()" method. There is a common criteria finder available and other remote managers don't expose this getById() methods either. We should keep the api consistent.
As discussed during today's hangout, bugs with 3.2.0 release should go to ON_QA, so I am moving it to ON_QA.
BZ for docuemtation/examples = https://bugzilla.redhat.com/show_bug.cgi?id=966125
This should be in a brew build since quite a while now.
Fixing target milestone
QE verified https://engineering.redhat.com/trac/jon/ticket/584