TLS guide repeats certs/ in the certificate directory
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 92/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown, shell
- Domain
- documentation
Research direction
Open docs/guides/tls-encryption.md at the certificate-generation example under the prerequisites section. Check that the cd path matches the directory created by the preceding mkdir, then verify the corrected command enters that directory; done when it exits successfully and prints the expected path.
Written by the indexing model from the issue text.
Description
Location: https://prometheus.io/docs/guides/tls-encryption/#pre-requisites
The certificate-generation example in docs/guides/tls-encryption.md creates /home/prometheus/certs/example.com, then tries to enter /home/prometheus/certs/certs/example.com:
mkdir -p /home/prometheus/certs/example.com && cd /home/prometheus/certs/certs/example.com
In a fresh Alpine 3.21.9 container with a writable /home/prometheus, this line exits 2:
sh: cd: line 0: can't cd to /home/prometheus/certs/certs/example.com: No such file or directory
Expected: cd enters the directory just created. Removing the repeated certs/ from the cd path makes the line exit 0; appending && pwd prints /home/prometheus/certs/example.com.
The reproduction executes only the directory-selection line. The following openssl command is a separate command; without errexit, the full pasted block can continue from the previous directory after cd fails.
- Dominant language
- TypeScript
- Stars
- 721
- Forks
- 1.2k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 18
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from prometheus/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
prometheus/docs#2285 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
prometheus/docs#2232 ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
prometheus/docs#2171 ·
Maintainers usually reply within 2 days
-
better 404 pageMay be free again A pull request for this issue was closed without being merged. Opengood first issue priority/p3 site
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
prometheus/docs#1795 · 2 comments ·
Maintainers usually reply within 2 days
-
Needs example of cluster wide inhibitionMay be free again A pull request for this issue was closed without being merged. Opendiataxis/howto
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
prometheus/docs#1353 · 5 comments ·
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
galaxyproject/loom#616 ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
redhat-developer/rhdh-plugin-export-overlays#4580 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
eknowledger/toolbench#266 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
devdotfast/whiteboard#1415 · 1 comment ·
Maintainers usually reply within 1 day