prometheus / prometheus/alertmanager
Feature Request: Convert the room_id string in the webex_config to a secret value.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
The room_id in the Webex configuration is a confidential parameter, but in the Prometheus documentation, it is expected as a string (as seen here: Prometheus Docs and webex.go), making it vulnerable on the internet. It would be more secure to include it under authorization within http_config, allowing it to be sourced from Kubernetes secrets.
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 with notify/webex/webex.go and the Prometheus configuration documentation linked in the issue, then compare the existing webex_config room_id handling with http_config authorization. The change is done when room_id can be represented as a secret-backed authorization value suitable for Kubernetes secrets and the documented configuration matches the supported behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100