[
https://issues.apache.org/jira/browse/MESOS-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated MESOS-1896:
-------------------------
Comment: was deleted
(was: www.rtat.net)
> Enable module specific command line parameters
> -----------------------------------------------
>
> Key: MESOS-1896
> URL: https://issues.apache.org/jira/browse/MESOS-1896
> Project: Mesos
> Issue Type: Improvement
> Components: modules
> Reporter: Till Toenshoff
> Assignee: Kapil Arya
> Priority: Major
> Fix For: 0.21.0
>
>
> h4. Idea
> Add a flags parameter to the create call and hand down textual or parsed JSON
> to the module. The JSON on the command line can either a) be associated with
> the module mention or it can b) be associated with the module kind's topic or
> c) have a separate flags section just for module flags.
> Opinions?
> h4. Examples (prototyping, not claiming this grammar is ideal):
> a) {noformat}slave --modules='[{lib : <path>, modules : [{name : "myModule",
> flags : '{credentials : "foo"}}]}]'{noformat}
> b) {noformat}slave --modules='[{lib : <path>, modules : [
> {"myModule"}]}]' --authenticatorFlags='{credentials : "foo"}'{noformat}
> c) {noformat}slave --modules='[{lib : <path>, modules : [{"myModule"}
> ]}]' --moduleFlags='[{module : "myModule", flags :
> {credentials : "foo"}
> ]}{noformat}
> In any case modules could report their required flags syntax when calling
> {noformat}slave --help --modules='[{lib : <path>, modules : [
> {"myModule"} ]}]'{noformat} or something like that in any of the above
> variants.
> This was copied from Bernd's comment on MESOS-1384.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
