feat: make postgres SSL certificate paths configurable #41
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the hardcoded certificate paths introduced in PR #40 by making the SSL certificate configuration fully customizable.
Changes
/home/coder/.postgresql
defaultssslrootcert
configurable: Now accepts custom certificate paths or can be left emptyvolumes
andvolumeMounts
configurable: Users can specify their own volume configurationsslrootcert
parameter gracefullyConfiguration Example
Users can now configure SSL certificates like this:
Breaking Change
This is a breaking change for users who relied on the hardcoded defaults. Users will need to explicitly configure SSL certificate paths if they use SSL connections.
Fixes the issue where certificate paths were hardcoded to
/home/coder/.postgresql/
.