[Improvement]: Accept the Moesif collector key as a Secret reference in Helm chart
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Gateway
Please select the aspect the issue is related to
Aspect/Configuration (Config files, settings, env vars, defaults)
Suggested Improvement
The Moesif collector key in the Gateway Helm chart is currently configured as a plaintext Helm value:
deployment:
enabled: true
replicaCount: 1
env:
gatewayControllerHost: ""
logLevel: info
moesifKey: ""
Since the Moesif collector key is sensitive, it should be referenced from a Kubernetes Secret instead of being provided directly as a Helm value.
Expected change
Support a Secret reference, for example:
deployment:
env:
moesifKeySecretRef:
name: ""
key: moesif-key
The Gateway should then read the Moesif collector key from the referenced Kubernetes Secret.
Related Issues
No response
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 locating the Gateway Helm chart's deployment values and templates, then trace how the moesifKey environment value reaches the Gateway. Render the chart with a Secret reference and verify that the generated deployment reads the collector key from the named Secret and key instead of requiring plaintext configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 74/100