mathieu-benoit / mathieu-benoit/score-openchoreo
Move resources's env vars related to dedicated dependencies's `envBindings`
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In here https://github.com/mathieu-benoit/score-openchoreo/blob/main/score-k8s/patchers/openchoreo.tpl#L75, move resources's env vars related to dedicated dependencies's `envBindings`.
Examples:
- https://github.com/openchoreo/openchoreo/blob/main/samples/gcp-microservices-demo/components/frontend-component.yaml#L38
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 in score-k8s/patchers/openchoreo.tpl around line 75 and compare the current resource environment-variable placement with the referenced OpenChoreo frontend-component.yaml example. Trace how dedicated dependencies and their envBindings are rendered. Done means those dependency-related environment variables appear in the intended moved location in the generated OpenChoreo manifests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100