[release/8.0-preview5] Rename config value to use unsecured instead of insecure #3241
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
JamesNK
requested review from
drewnoakes,
davidfowl,
joperezr,
kvenkatrajan and
mitchdenny
mitchdenny
approved these changes
Mar 28, 2024
davidfowl
approved these changes
Mar 28, 2024
JamesNK
reviewed
Mar 28, 2024
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #3233 to release/8.0-preview5
/cc @JamesNK
Customer Impact
Makes config name consistent with other config names which use unsecured. Should be changed for P5 because people will end up explicitly specifying it.
Testing
Unit tests and manual testing
Risk
Low