aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maxim Khutornenko <ma...@apache.org>
Subject Re: Constraining the environment field
Date Tue, 15 Dec 2015 17:46:16 GMT
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 <wfarner@apache.org> 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 <chrislambert@gmail.com>
> 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
>>

Mime
View raw message