Adding spec.metadata.pemContents to MySQL Binding #3620
+320
−30
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
Signed-off-by: Ed <[email protected]>
edwardfward
force-pushed
the
add-pem-contents
branch
from
8fec658 to
5991b8f
Compare
7 tasks
Signed-off-by: Ed <[email protected]>
edwardfward
changed the title
* moved mysql.RegisterTLSConfig ahead of mysql.ParseDSN * added unit tests for InitDB to check for PEM and ParseDSN errors Signed-off-by: Ed <[email protected]>
edwardfward
changed the title
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.
Description
Incorporated
spec.metadata.pemContentsto MySQL binding to provide a means to build SSL-secured bindings for apps deployed in Azure Container Apps.Issue reference
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: