💥 Only enable native roots if CA override not specified #1007
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.
What was changed
Don't enable native TLS roots if a CA override is specified. This is technically breaking, but only if you were doing a somewhat odd thing in the first place.
Why?
People using CA overrides often want to do it in an environment where there are no native roots, which this change enables.
Checklist
Closes [Bug] Native certs used for TLS client even when server root CA override present #1004
How was this tested:
Could not come up with any kind of reasonable test that wasn't dramatically more LOC than it feels worth. Open to ideas.
Any docs updates needed?