]
James Strachan commented on WFCORE-433:
---------------------------------------
[~harald.pehl] ah that sounds great. Yeah the management console + the back end could be
the same pod, which might help any CORS issues.
We probably also need to check the security stuff too; so that an authenticated user in
the OpenShift console can start using the WF management console if they have the right
karma and we get SSO but proper ACLs and stuff. I remember folks had to tinker a little
with hawtio / jolokia for the "Java console" part in the OpenShift console when
you look inside the JMX view of a JVM with jolokia port exposed to view JMX / Camel routes
et al - we had to get the back end to generate a new token with OpenShift to ensure things
were properly secure etc.
git backend for loading/storing the configuration XML for wildfly
-----------------------------------------------------------------
Key: WFCORE-433
URL:
https://issues.jboss.org/browse/WFCORE-433
Project: WildFly Core
Issue Type: Feature Request
Components: Domain Management
Reporter: James Strachan
Assignee: Jason Greene
when working with wildfly in a cloud/paas environment (like openshift, fabric8, docker,
heroku et al) it'd be great to have a git repository for the configuration folder so
that writes work something like:
* git pull
* write the, say, standalone.xml file
* git commit -a -m "some comment"
* git push
(with a handler to deal with conflicts; such as last write wins).
Then an optional periodic 'git pull' and reload configuration if there is a
change.
This would then mean that folks could use a number of wildfly containers using docker /
openshift / fabric8 and then have a shared git repository (e.g. the git repo in openshift
or fabric8) to configure a group of wildfly containers. Folks could then reuse the wildfly
management console within cloud environments (as the management console would, under the
covers, be loading/saving from/to git)
Folks could then benefit from git tooling when dealing with versioning and audit logs of
changes to the XML; along with getting the benefit of branching, tagging.