prometheus / prometheus/exporter-toolkit
Unify TLS settings in prometheus/common
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 311
- Forks
- 109
- Avg merge
- 3d 59m
- Merged PRs (30d)
- 6
Description
We have server-side TLSConfig in exporter-toolkit/web, and client-side TLSConfig in common/config.
Exporter-toolkit is marked as "currently WIP and experimental".
We should factor it out, enable common config changes, e.g. disable TLS 1.0 more easily.
At the Prometheus 2023 Dev Summit 06 meeting it was agreed to move the TLS handling into common.
Ref #157.
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 comparing the server-side TLSConfig in exporter-toolkit/web with the client-side TLSConfig in common/config. Review the linked Dev Summit decision and Ref #157 for context. Done means TLS handling is moved into common and common configuration changes can be applied consistently, including easier TLS 1.0 disabling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100