[
https://issues.apache.org/jira/browse/AURORA-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486594#comment-14486594
]
Bill Farner commented on AURORA-1264:
-------------------------------------
IMHO this is ~impossible to sanely manage without effectively having a
configuration schema, i.e. a hierarchical configuration file. I'm not strictly
against that, and at some point that may be the only way to make scheduler
configuration sane as more config combinations are possible.
> command-line flags framework leads to confusing valid configurations
> --------------------------------------------------------------------
>
> Key: AURORA-1264
> URL: https://issues.apache.org/jira/browse/AURORA-1264
> Project: Aurora
> Issue Type: Story
> Components: Scheduler, Usability
> Reporter: Kevin Sweeney
> Priority: Minor
>
> Right now it's possible to specify flags that have no meaning unless another
> flag is turned up. For example:
> {noformat}
> -enable_api_security=true
> -shiro_ini_path=/etc/aurora/shiro.ini
> -shiro_realm_modules=org.apache.aurora.scheduler.http.api.security.Kerberos5RealmModule
> {noformat}
> does nothing and has no warning. The correct form is *obviously*:
> {noformat}
> -enable_api_security=true
> -shiro_ini_path=/etc/aurora/shiro.ini
> -shiro_realm_modules=org.apache.aurora.scheduler.http.api.security.Kerberos5RealmModule,org.apache.aurora.scheduler.http.api.security.IniShiroRealmModule
> {noformat}
> Investigate changes to our command-line framework that would get us a better
> error message here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
