SQC-333: Support Hyperdrive with SSL in dev mode #3037
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
thomasgauvin
approved these changes
Oct 31, 2024
a-robinson
approved these changes
Oct 31, 2024
jasnell
approved these changes
Nov 3, 2024
anonrig
approved these changes
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We have historically used sslmode=disable in when running
wrangler dev, with the intention of not forcing folks to set up SSL on a local test DB. Unfortunately this causes friction because many hosted databases will have SSL set up and required, and Hyperdrive in production actually requires this. To improve flexibilty, switch toprefermode which will use SSL if available for a close-to-production experience, but will allow unencrypted connections if needed.