uselagoon / uselagoon/remote-controller
Advanced task specific environment variables
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
With #185 we mounted the standard environment variables into advanced tasks.
There has been some discussion about supporting advanced task specific environment variables to inject details that we might not want available in, say, a cli pod.
This should be fairly simple to implement - the question is, where and how?
Currently we inject the JSON_PAYLOAD with whatever details come through from the invocation of the advanced task - if we piggy-back on that, we could move the entire logic into uselagoon/lagoon. Alternatively, we could extend the advanced task implementation to support a separate set of variables (also passed with the task information).
Thoughts?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing where JSON_PAYLOAD and standard environment variables are injected for advanced tasks, reviewing #185 and the advanced-task implementation; first agree whether the data belongs in uselagoon/lagoon or a separate task-variable set. Done means the chosen design injects task-specific variables into advanced tasks without exposing them to unrelated pods such as cli.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100