I suppose we'll need to use "oc update -f $template" and track our clusterquota templates (oc edit and oc patch aren't the nicest things to idempotently automate). The nice thing about having --dry-run associated is at least we wouldn't have to maintain YAML templates, and we could rely on the API to generate object files for us. I can file an RFE and see what makes sense there.
Thanks, Ben Pritchett On Tue, Nov 8, 2016 at 11:12 AM, David Eads <[email protected]> wrote: > All the basic CRUD commands work, so you can run `oc > edit clusterquota/name`, `oc patch clusterquota/name <your patch>`, or `oc > update -f <your file>`. > > On Tue, Nov 8, 2016 at 11:06 AM, Ben Pritchett <[email protected]> > wrote: > >> Is there a method for updating clusterquotas that have already been >> created? Referencing the creation process here: >> https://docs.openshift.com/container-platform/3.3/admin_guid >> e/multiproject_quota.html#multi-project-quotas-selecting-projects >> >> There isn't a "oc update clusterquota foo" and the workaround for >> configmaps doesn't seem to work due to missing --dry-run option. The >> workaround for configmaps is below: >> >> oc create configmap foo --from-file=haproxy-config.template --dry-run -o >> yaml | oc update -f - >> >> Trying to automate this for a large cluster buildout, where we'll need >> per-user clusterquota definitions for self-provisioning. >> >> Thanks, >> >> Ben Pritchett >> >> _______________________________________________ >> users mailing list >> [email protected] >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
