Decide whether we want to leave `global.secureCookieKey` around
Open
Nobody has claimed this yet.
team: workbench
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
The global.secureCookieKey value was originally devised so that a dedicated Launcher chart and the Workbench chart could share the value.
However, we are moving away from that pattern, so perhaps we should deprecate the value / warn about its use, and prepare to remove it?
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 by tracing the global.secureCookieKey value across the Launcher and Workbench charts and reviewing how the two charts currently share it. Done means the project has a clear decision on whether to retain, deprecate with a warning, or remove the value, along with the resulting scope of work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100