Well yeah that is an option but then that is more or less like "oc edit scc" which is not what i want since i need to know all the users and that is tricky depending on the time when i run it (green field deployment, after upgrade etc)
On Thu, May 24, 2018 at 10:24 PM, Mateus Caruccio < mateus.caruc...@getupcloud.com> wrote: > Hey, you could use oc's --loglevel=N to see the exact HTTP > request/response flow with the api and adapt it to your need. > I believe a level of 8 should be enough. > > -- > Mateus Caruccio / Master of Puppets > GetupCloud.com > We make the infrastructure invisible > Gartner Cool Vendor 2017 > > 2018-05-24 18:16 GMT-03:00 Daniel Comnea <comnea.d...@gmail.com>: > >> Hi, >> >> Is any alternative to "oc adm policy add-scc-to-user" command in the >> same way there is one for "oc create serviceaccount foo" which can >> be achieved by >> >> apiVersion: v1 >> >> kind: ServiceAccount >> >> metadata: >> >> name: foo-sa >> >> namespace: foo >> >> >> I'd like to be able to put all the info in a file rather than run oc cmd >> sequentially. >> >> >> Thanks >> >> >> _______________________________________________ >> dev mailing list >> dev@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev >> >> >
_______________________________________________ dev mailing list dev@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
