[jboss-jira] [JBoss JIRA] (WFCORE-433) git backend for loading/storing the configuration XML for wildfly
ehsavoie Hugonnet (JIRA)
issues at jboss.org
Fri Feb 19 12:24:00 EST 2016
[ https://issues.jboss.org/browse/WFCORE-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165938#comment-13165938 ]
ehsavoie Hugonnet edited comment on WFCORE-433 at 2/19/16 12:23 PM:
--------------------------------------------------------------------
For reference only
Creating a configmap:
{noformat}
curl -H "Content-Type: application/json" -X POST -d '{"kind":"ConfigMap", "metadata":{"name":"test-configmap"}, "data": {"data-1":"value-1", "data-2": "value-2"}}' http://localhost:8080/api/v1/namespaces/widlfy-test/configmaps
{noformat}
Which creates;
{noformat}
{
"kind": "ConfigMap",
"apiVersion": "v1",
"metadata": {
"name": "test-configmap",
"namespace": "widlfy-test",
"selfLink": "/api/v1/namespaces/widlfy-test/configmaps/test-configmap",
"uid": "03335f37-d729-11e5-bb11-3c970e964876",
"resourceVersion": "863",
"creationTimestamp": "2016-02-19T16:51:25Z"
},
"data": {
"data-1": "value-1",
"data-2": "value-2"
}
}
{noformat}
was (Author: ehugonnet):
For reference only
Creating a configmap:
curl -H "Content-Type: application/json" -X POST -d '{"kind":"ConfigMap", "metadata":{"name":"test-configmap"}, "data": {"data-1":"value-1", "data-2": "value-2"}}' http://localhost:8080/api/v1/namespaces/widlfy-test/configmaps
Which creates;
{noformat}
{
"kind": "ConfigMap",
"apiVersion": "v1",
"metadata": {
"name": "test-configmap",
"namespace": "widlfy-test",
"selfLink": "/api/v1/namespaces/widlfy-test/configmaps/test-configmap",
"uid": "03335f37-d729-11e5-bb11-3c970e964876",
"resourceVersion": "863",
"creationTimestamp": "2016-02-19T16:51:25Z"
},
"data": {
"data-1": "value-1",
"data-2": "value-2"
}
}
{noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list