Hi everyone,

I have been wondering about the environment part of Aurora jobkeys (devel, 
test, staging, staging1, ...prod). 

I guess you made the environment a first class citizen in order to enforce some 
kind of standardization. How is this working out for you in practice? 

IIRC, the current set of supported environment names is enforced by the client. 
In general, would you be opposed to moving this validation to the scheduler, so 
that it can be configured cluster wide? This would enable us to introduce 
environment names which are closer to our domain and organization.  Or is this 
even somewhat covered in the upcoming job tier implementation?

Thanks for your input,
Stephan

Reply via email to