helm-reval chart ignores documented JWT auth values
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Problem
The ReVal application and chart README use auth.jwt.*, but the chart defaults and ConfigMap template still read and render the JWT fields directly under auth.*. Setting the documented reval.serviceConfig.auth.jwt.enabled=true value therefore does not enable the local JWT authorizer in the generated ReVal configuration.
Expected behavior
The chart should expose JWT settings under reval.serviceConfig.auth.jwt and render them beneath auth.jwt in config.yaml.
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 helm-reval chart README, chart defaults, and ConfigMap template, then compare the documented reval.serviceConfig.auth.jwt values with the generated config.yaml. Update the chart so JWT settings are exposed under reval.serviceConfig.auth.jwt and rendered beneath auth.jwt, then verify that enabling the documented value produces the expected ReVal configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100