cloudfoundry / cloudfoundry/nodejs-buildpack
BOSH configured custom trusted certificate support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 174
- Forks
- 389
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
it seems that since https://github.com/cloudfoundry/nodejs-buildpack/pull/463
As a temporary solution the environment variable
SSL_CERT_DIRis set with the default SSL dir (/etc/ssl/certs) when installing Node >=18.0.0.
BOSH configured custom trusted certificate support is implicitly enabled as the BOSH configured custom trusted certificate ends up in /etc/ssl/certs.
This is great!
It might even be that setting SSL_CERT_DIR is not even needed anymore: https://github.com/nodejs/node/issues/43560
Could the support of BOSH configured custom trusted certificates be documented at https://docs.cloudfoundry.org/buildpacks/node/index.html#bosh_trusted_cert ?
Thank you and best regards,
Silvestre
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 at the BOSH trusted certificate section of the Node.js buildpack documentation linked in the issue, and review the referenced nodejs-buildpack pull request and Node.js issue for context. Document that BOSH-configured custom trusted certificates are supported, and ensure the section accurately explains the current behavior and any SSL_CERT_DIR requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 62/100