[
https://issues.apache.org/jira/browse/AURORA-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431391#comment-15431391
]
Joshua Cohen commented on AURORA-1750:
--------------------------------------
The executor should already have access to the task metadata. {{launchTask}}
receives a {{TaskInfo}} proto whose data is a serialized Aurora
{{AssignedTask}} thrift struct. From there it's just a question of reading the
metadata from assigned task's {{TaskConfig}} property.
> Expose Aurora task metadata to thermos task
> -------------------------------------------
>
> Key: AURORA-1750
> URL: https://issues.apache.org/jira/browse/AURORA-1750
> Project: Aurora
> Issue Type: Task
> Reporter: Zameer Manji
> Priority: Minor
>
> Much like how we expose mesos hostname, aurora instance number, etc to
> thermos I think we should be able to expose Aurora task metadata to thermos
> tasks.
> I don't forsee complexity or harm for this, but it allows users to plumb more
> information into the task. For example, one could encode a 'package version'
> or 'build pipeline' or 'audit pipeline' metadata into the task. The task
> could then expose this to others or act differently if required.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
