opsiClient should be object group compliant
That means:
- In a object group, the opsiClient tab must appear if and only if all objects are windows hosts
- When activating opsiClient on an object group, it must trigger OPSI.update_or_insert on all members
- When removing opsiClient from a winstation that is in an objectGroup with opsi activated should not call delete on the OPSI host
(from redmine: issue id 2328, created on 2013-04-18, closed on 2013-04-19)
- Changesets:
- Revision eb0f6825 by Côme Chilliet on 2013-04-18T16:09:55.000Z:
Fixes: #2328 opsiClient should be object group compliant
- Revision c41cb658 by Côme Chilliet on 2013-04-19T10:20:52.000Z:
Fixes: #2328 OPSI.delete action can now take a list of mac
- Revision db81e91c by Côme Chilliet on 2013-04-19T12:21:14.000Z:
Fixes: #2328 OPSI.delete action can now take a list of mac
- Revision 3772b0da by Côme Chilliet on 2013-04-19T13:21:10.000Z:
Fixes: #2328 OPSI.delete action can now take a list of mac
- Revision 8f034015 by Côme Chilliet on 2013-04-19T14:21:43.000Z:
Fixes: #2328 prevent from undef $params