Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-433

git backend for loading/storing the configuration XML for wildfly


    • Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.0.0.Beta1
    • Component/s: Management
    • Labels:


      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.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  ehugonnet Emmanuel Hugonnet
                  jastrachan James Strachan
                • Votes:
                  2 Vote for this issue
                  17 Start watching this issue


                  • Created: