Allow for custom certificate file paths.
Open
@Vonng is already working on this.
Since Jun 8, 2025.
API
PGSQL
- Dominant language
- Shell
- Stars
- 5.7k
- Forks
- 384
- Avg merge
- 2h 36m
- Merged PRs (30d)
- 2
Description
Currently patroni and Postgresql configuration use hardcoded paths for tls certificates. It would be more convenient if these were exposed as variables for use with custom certificates and certificate automation. Further the ca_file path for both instances is not mandatory if the root certificate is provided in the system trust store and the certificate contains the full chain.
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.
Assessment
This issue has not been assessed yet.