uselagoon / uselagoon/remote-controller
Inject remote-controller version into build and task pods
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
Similarly to how the lagoon-core version is passed to builds, injecting the remote-controller version into a build could be useful in the future for compatibility checks.
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
Start by tracing how the lagoon-core version is passed into builds, then identify the corresponding build and task pod entry points. Confirm where the remote-controller version should be injected and how pod configuration is tested; done means both pod types expose that version for future compatibility checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100