Mostly we wanted to do it as part of git, but not enough clear flows that supported it. For instance, deploying the same repo to multiple projects or clusters. Or whether we should be more on the simple flow (like heroku) or be more flexible.
I started a PR exploring this earlier this year - it's not that some sort of context is terrible, but being careful not to go too far. I'd ask you guys - what sorts of workflows do you have today that are single target? What sorts of workflows beyond the ones mentioned would work well with contexts? On Dec 14, 2016, at 6:54 PM, Mateus Caruccio <mateus.caruc...@getupcloud.com> wrote: It makes total sense to me having a local context config for the cluster, just like git with .git/. People is used to it and as it's already common on most languages/framework like python's requirements.txt/setup.py, ruby's Gemfile, node's packages.json and so on. Clayton, could you please elaborate a little bit on the downsides you've mentioned or point for the discussion thread? -- Mateus Caruccio / Master of Puppets GetupCloud.com - Eliminamos a Gravidade On Wed, Dec 14, 2016 at 8:24 PM, Ben Parees <bpar...@redhat.com> wrote: > > > On Wed, Dec 14, 2016 at 5:17 PM, Graham Dumpleton <gdump...@redhat.com> > wrote: > >> >> On 15 Dec 2016, at 9:06 AM, Ben Parees <bpar...@redhat.com> wrote: >> >> >> >> On Wed, Dec 14, 2016 at 4:53 PM, Clayton Coleman <ccole...@redhat.com> >> wrote: >> >>> The process command does now include an "--env-file" option - so you >>> could do "oc process -f template-file.yaml --env-file .oc_env | oc apply -f >>> -" >>> >> >> I think Phillipe is looking for a "cluster environment definition" file >> which controls what cluster+namespace the resources are "applied" to, not >> env variable inputs to the template processing, but that's basically what >> the .kube/config file specifies/controls today (ie it controls what >> cluster+project your oc commands are going to operate against) >> >> >> The problem being though that it can only refer to one cluster at a time. >> Thus you can easily stuff up when have multiple windows open against apps >> for different clusters or users and you forgot that you had changed which >> one you were logged in to. Yes, you can use --cluster=‘’ option (if that >> works how I think), but still have to remember to add it explicitly, where >> as if you could capture that in a configuration file in the repo itself and >> oc would look for it in some way you could be sure you were always working >> against correct cluster. >> >> BTW, I can’t find any docs about —env-file in oc help strings for that >> command. Also just noticed that ‘oc options’ sends output to stderr and not >> stdout which is a bit strange. If using —help on a command still goes to >> stdout. >> > > -- > env-file support just merged (today, I think, or this week anyway). > Clayton is, as always, on the cutting edge of functionality. > > > > >> >> Graham >> >> >>> On Wed, Dec 14, 2016 at 4:06 PM, Philippe Lafoucrière < >>> philippe.lafoucri...@tech-angels.com> wrote: >>> >>>> Hi, >>>> >>>> We're having fun with the "oc apply" command, which solves a lot of >>>> configuration issues we've had in the past. >>>> There's just one thing I would like to have in oc: a local .oc_env file >>>> to define some defaults, like: >>>> >>>> - Current cluster url (make sure we're hitting the production cluster, >>>> not any of the test clusters) >>>> - Current namespace (to make sure apply won't fu.. up another project >>>> if we forget to specify it). >>>> >>>> Is there something we could see in the future? >>>> >>>> Thanks, >>>> Philippe >>>> >>>> -- >>>> Philippe Lafoucrière - CEO >>>> http://www.tech-angels.com >>>> https://gemnasium.com >>>> France : +33 (0) 3 65 96 02 92 >>>> Canada: +1 (418) 478-1175 <%28418%29%20478-1175> >>>> USA: +1 (954) 607-7443 <%28954%29%20607-7443> >>>> >>>> >>>> >>>> _______________________________________________ >>>> users mailing list >>>> users@lists.openshift.redhat.com >>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>>> >>>> >>> >>> _______________________________________________ >>> users mailing list >>> users@lists.openshift.redhat.com >>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>> >>> >> >> >> -- >> Ben Parees | OpenShift >> >> _______________________________________________ >> users mailing list >> users@lists.openshift.redhat.com >> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >> >> >> > > > -- > Ben Parees | OpenShift > > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > > _______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
