I think organizations should be able to choose whether to restrict environments, so i would not seek to disable that.
On Tue, Dec 15, 2015 at 12:50 PM, Chris Lambert <[email protected]> wrote: > Thanks for the quick responses! I don't think we have a more urgent need > for this than Q1, as we're still evaluating how to construct our jobkeys. > > Will arbitrary environments still be supported? It's not clear what the > intent is from the doc linked in that ticket. > > > > On Tue, Dec 15, 2015 at 10:05 AM, Bill Farner <[email protected]> wrote: > > > Of course, we could do the env restriction well before that work. > > > > On Tuesday, December 15, 2015, Maxim Khutornenko <[email protected]> > wrote: > > > > > The allowed set of env values will be restricted as part of > > > https://issues.apache.org/jira/browse/AURORA-1443. This work will > > > include moving environment definitions to the scheduler side and > > > connecting them to tier definitions. We are planning this work for Q1. > > > > > > On Tue, Dec 15, 2015 at 9:22 AM, Bill Farner <[email protected] > > > <javascript:;>> wrote: > > > > Within the scheduler there is not. The client currently applies > > > convention > > > > there. I'd see this as a perfectly valid feature request and a > > > relatively > > > > easy one to fulfill, happy to help guide. > > > > > > > > On Tue, Dec 15, 2015 at 9:20 AM, Chris Lambert < > [email protected] > > > <javascript:;>> > > > > wrote: > > > > > > > >> Is there a method for constraining the environment field to a > > > >> pre-determined set of values? It appears to be just a string [1], > but > > > IIRC > > > >> there was some validation possible somewhere to prevent arbitrary > > > values. > > > >> > > > >> Chris > > > >> > > > >> [1] > > > >> > > > >> > > > > > > https://github.com/apache/aurora/blob/master/api/src/main/thrift/org/apache/aurora/gen/api.thrift#L132 > > > >> > > > > > >
