Add in-memory PEM bytes client SSL config variants - #4282
Open
shuch3ng wants to merge 2 commits into
Open
Conversation
shuch3ng
requested review from
987Nabil,
jdegoes,
kyri-petrou and
vigoo
as code owners
September 2, 2026 09:51
✅ Deploy Preview for zio-http ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Member
|
@shuch3ng Please run |
shuch3ng
force-pushed
the
ft-support-in-memory-ssl-config
branch
from
September 5, 2026 09:34
b19ab3b to
bcdaf23
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds byte-based alternatives to the existing file and resource based client SSL configs, so callers can supply certificates and keys that are already in memory (e.g. loaded from a vault or secret manager) instead of requiring an on-disk path or classpath resource.
Closes #4281