cloudfoundry / cloudfoundry/prometheus-boshrelease
[Prometheus] Migrate pre-start logic to regular .erb handling
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 120
- Forks
- 175
- PR merge metrics
- No merged PRs in 30d
Description
This is a follow up of integrating Prometheus3 into the Bosh Release.
At the moment we use the pre-start script of the Prometheus job to create various certificate files on the filesystem.
Please check if we can migrate away from that to maybe use something similar as https://github.com/cloudfoundry/haproxy-boshrelease/blob/master/jobs/haproxy/templates/certs.ttar.erb
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 jobs/prometheus/templates/bin/pre-start.erb and read how it creates certificate files. Compare that approach with jobs/haproxy/templates/certs.ttar.erb in the linked haproxy-boshrelease, then determine whether regular .erb handling fits here. Done means certificate setup no longer depends on the Prometheus pre-start script while preserving the release behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100