clarify documentation around stringMatch and case-sensitivity #3304
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: Ian Rudie <ian.rudie@solo.io>
istio-testing
added
the
size/XS
ilrudie
added
the
release-notes-none
|
/retest |
ilrudie
added
the
cherrypick/release-1.23
|
1.22 has the same verbiage, we could consider cherry-picking the doc update for it as well |
howardjohn
approved these changes
Sep 5, 2024
|
In response to a cherrypick label: new pull request created: #3305 |
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.
seeks to add clarification around case-sensitive vs case-insensitive options for stringMatch in the VirtualService API