[
https://issues.apache.org/jira/browse/MESOS-8357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302484#comment-16302484
]
Till Toenshoff commented on MESOS-8357:
---------------------------------------
After contemplating a bit more, the best fitting new prefix for those
environment variables appears to be {{MESOS_EXAMPLE_}} as it is verbose,
deterministic and has low risk of collisions.
> Example frameworks have an inconsistent UX.
> -------------------------------------------
>
> Key: MESOS-8357
> URL: https://issues.apache.org/jira/browse/MESOS-8357
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: Till Toenshoff
> Assignee: Till Toenshoff
> Priority: Minor
>
> Our example frameworks are a bit inconsistent when it comes to specifying
> things like the framework principal / secret etc..
> Many of these examples have great value in testing a Mesos cluster. Unifying
> the parameterizing would improve the user experience when testing Mesos.
> {{MESOS_AUTHENTICATE_FRAMEWORKS}} is being used by many examples for enabling
> / disabling authentication. {{load_generator_framework}} as one example
> however uses {{MESOS_AUTHENTICATE}} for that purpose. The credentials
> themselves are most commonly expected in environment variables
> {{DEFAULT_PRINCIPAL}} and {{DEFAULT_SECRET}} while in some cases we chose to
> use {{MESOS_PRINCIPAL}}, {{MESOS_SECRET}} instead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
