[
https://issues.apache.org/jira/browse/MESOS-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032258#comment-15032258
]
Jojy Varghese commented on MESOS-3787:
--------------------------------------
[[email protected]], [~sdegler]
Looks like a hybrid approach could work :
Have the container json configuration values be expanded before being applied.
In this case for example, the "volume" configuration could be expanded first
before being processed ( at L432 - L439). So something like:
{code}
if (volume.has_host_path()) {
const string expandedHostPath = expand(volume.host_path());
const string expandedVolume = expand(volumeConfig);
...
}
{code}
This approach could be expanded to other variables also.
> As a developer, I'd like to be able to expand environment variables through
> the Docker executor.
> ------------------------------------------------------------------------------------------------
>
> Key: MESOS-3787
> URL: https://issues.apache.org/jira/browse/MESOS-3787
> Project: Mesos
> Issue Type: Wish
> Reporter: John Garcia
> Labels: mesosphere
> Attachments: mesos.patch, test-example.json
>
>
> We'd like to have expanded variables usable in [the json files used to create
> a Marathon app, hence] the Task's CommandInfo, so that the executor is able
> to detect the correct values at runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
