Evaluate moving all Values.*.existingSecrets into Values.config.existingSecrets
Open
Nobody has claimed this yet.
team: workbench
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
Description
Evaluate if it makes sense to move all .Values.*.existingSecrets into .Values.config.existingSecrets instead, as suggested by @bschwedler https://github.com/rstudio/helm/pull/736/files#r2534897252
Contributor guide
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 with the linked pull request discussion and inspect the chart values that define .Values.*.existingSecrets and .Values.config.existingSecrets. Done means reaching a project-supported decision on whether to consolidate these values and documenting the required scope and migration implications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100