[jboss-jira] [JBoss JIRA] (WFWIP-253) With operator it is not possible to mount configMap to $JBOSS_HOME/extensions

[Ken Wills (Jira)]

    [ https://issues.jboss.org/browse/WFWIP-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801083#comment-13801083 ] 

Ken Wills commented on WFWIP-253:
---------------------------------

[~jmesnil] These are executed via openshift-launch:

https://github.com/jboss-container-images/jboss-eap-modules/blob/7.3.x-legacy/os-eap7-launch/added/openshift-launch.sh#L4
https://github.com/jboss-container-images/jboss-eap-modules/blob/7.3.x-legacy/os-eap-launch/added/launch/configure.sh#L114

$JBOSS_HOME/extensions is the required location for it, its special in the sense that when it runs all other configuration should be completed, and any remaining XML markers etc in teh config file are no longer required etc. So on EAP 7.2, for example it would be safe to run the embedded CLI at this point, and not be concerned about XML markers / comments being dropped from the config.

> With operator it is not possible to mount configMap to $JBOSS_HOME/extensions
> -----------------------------------------------------------------------------
>
>                 Key: WFWIP-253
>                 URL: https://issues.jboss.org/browse/WFWIP-253
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Simka
>            Assignee: Jeff Mesnil
>            Priority: Major
>              Labels: operator
>
> With operator it is not possible to mount configMap to $JBOSS_HOME/extensions. Which is supported way how to run postconfigure scripts. 
> See: https://issues.jboss.org/browse/EAP7-892?focusedCommentId=13684369&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13684369
> Operator mounts all configMaps to {{/etc/configmaps}}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)