Jay Buffington created AURORA-319:
-------------------------------------
Summary: Allow job environments other than prod, devel, test or
staging<number>
Key: AURORA-319
URL: https://issues.apache.org/jira/browse/AURORA-319
Project: Aurora
Issue Type: Bug
Components: Client
Reporter: Jay Buffington
Priority: Minor
git commit bcabfce6 introduced limitations on what job environments must be
named. Are these names arbitrary or is there some policy attached to these
names?
I suspect they are not arbitrary because I believe aurora will preempt tasks
that are not in the prod environment to make room for jobs that are.
What would the ramifications be of removing the "_validate_environment_name"
function from src/main/python/apache/aurora/client/config.py ? Are there
reasons why this was introduced in the first place?
--
This message was sent by Atlassian JIRA
(v6.2#6252)