-
Feature Request
-
Resolution: Won't Do
-
Major
-
None
-
None
the EAP/Wildfly should be extracted to a separate subtype entity/class of Middleware server. currently it is of type Middleware server and is differentiated by product field. Looking forward with more entities like Fuse to be added, we need to subtype it more properly.
EAP and wildfly can be on the same subtype and still be differentiated by product for name/icon difference, no need in 2 new subtypes.
from user perspective everything should remain the same in UI, users don't care if this is the same class with a different field or some classes hierarchy. The need to see same "wildfly/eap" etc server, its correct version and the right icon.
So, you might also need after the db part to adjust some code related to icons, as right now it relies on current design where everything is the same class. (check this part with Karel)
https://github.com/ManageIQ/manageiq-ui-classic/blob/master/app/decorators/middleware_server_decorator.rb
- blocks
-
HAWKULAR-1253 add a predefined scope where product == EAP so users can apply it to a policy
- Resolved
-
HAWKULAR-1247 Enable Compliance and Control policies for Middleware servers and EAP servers
- Resolved