Add optional TLSConfiguration parameter to Postgres' configuration initializer #187
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.
A user should be able to call
PostgresConfiguration(url:tlsConfiguration:).In environment like Heroku, where only a
DATABASE_URLis given and some databases required SSL on, we should be able to add theTLSConfigurationright on when creating thePostgresConfiguration. Simply addingsslmode=requireto the URL does not work as the default TLSConfiguration has TLS verification on.Related to #186.