[
https://issues.redhat.com/browse/WFWIP-329?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFWIP-329:
----------------------------------------
Does this bring much benefit relative to the potential complexity and bugs?
In a slimmed context, the
https://github.com/wildfly/wildfly/pull/13343 web-console layer
either is or is not present. If it is present the user specified it and we presumably
don't want to turn it off. And if it is not, given the fix to WFCORE-5073, leaving
the console-enabled attribute undefined (default to true) doesn't do much harm.
Ideally the 'management' layer would set console-enabled to false and the
web-console layer, which depends on management, would set it to true. But I don't know
if Galleon would handle that correctly -- two layers specifying different values for the
same attribute.
Bootable JAR - Cloud - Disable management console in mgmt
http-interface
------------------------------------------------------------------------
Key: WFWIP-329
URL:
https://issues.redhat.com/browse/WFWIP-329
Project: WildFly WIP
Issue Type: Bug
Reporter: Jean Francois Denise
Assignee: Jean Francois Denise
Priority: Major
The console is disabled for config run in EAP/XP s2i builder image. It makes sense to
apply the same change for Bootable JAR when cloud is enabled. So a CLI script will run to
disable it (if management interface exists):
/core-service=management/management-interface=http-interface:write-attribute(name=console-enabled,value=false)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)