Support for platform variables field in task drivers
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
@tgross had a nice idea for handling platform-specific plumbing of data through to executors that we might not want exposed to task runtime environments, `PlatformVariables`. Currently we're just making use of `Env` to pass uninteresting fields to the executor that are uninteresting to the task.
https://github.com/hashicorp/nomad/pull/12419#discussion_r843126108
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the PlatformVariables proposal and the linked discussion in pull request 12419, then trace how task drivers currently use Env to pass data to executors. Determine the intended driver and executor boundaries, and define done as supporting platform-specific variables without exposing them to task runtime environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100