ServerGroup assignment for a deployment can be accomplished in 2 places, as a scheduled operation (Operations tab) or configuration update (Configuration tab). I'm in favor of making it a configuration update. Less potential confusion.
Version-Release number of selected component (if applicable):
4.12 snapshot ed8a2c4
If we can suppress this from the user-interface and officially "deprecate" the operation, that would be ideal.
Due to backward compatibility with user defined remote API calls or alert notifications, I don't think we should make the operation dispensary in 3.x. But having an operation and now this configuration managed via configuration, doesn't make sense to expose both of them via the UI and we should be pushing users to use the configuration.
At least I can but "Deprecated" to operation's description. Would it be good enough? Otherwise I'd have to introduce new attribute in plugin descriptor.
Yes. That would work. Something like "Deprecated: Use server-group property found in resource configuration instead."
Also be sure to mark the operation as deprecated or whatever else is necessary to ensure that it is no longer documented in future builds of the resource reference guide.
@John, what do we need to do to get a release note captured for this change? Perhaps that is already being done via JON3-25/PRODMGT-368?
Author: Libor Zoubek <email@example.com>
Date: Thu Jun 26 23:44:31 2014 +0200
Bug 1104818 - [JON3-25] Duplicate functionality in Operations &
Deprecate "Assign To Server-Group" operation
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
verified in JON 3.3 ER02
Created attachment 936451 [details]