I'm trying to figure out how to manage OpenShift apps from an "Infrastructure as code" perspective.
The obvious place to start is by keeping the yaml or json representation of all OpenShift objects as files under source control. But people can still edit objects via the Web console (and sometimes that will be the most convenient route in development). So at some point you will need to get the yaml files in source control up-to-date. The problem is, `oc get -o yaml` has a lot of output that one wouldn't want to keep under source control. For example creationTimestamp, resourceVersion, selfLink and uid seem redundant to me - if I need to recreate the same logical app from source, or update testing to look like development, I don't care if the objects have the same timestamps and uids they used to have. So you need to postprocess the output of `oc get` to transform it into suitable source, you can't just pipe the output of `oc get` to overwrite your source files. Before I reinvent the wheel on anything, does anyone know if there are existing solutions? -- Pieter Nagel Lautus Solutions (Pty) Ltd Building 27, The Woodlands, 20 Woodlands Drive, Woodmead, Gauteng 0832587540
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
