-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Add ability to filter ConfigDump. #16774
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
818ec8d
Add ability to filter ConfigDump.
paul-r-gall c9712c3
Merge remote-tracking branch 'upstream/main' into FilterConfigDump
paul-r-gall 56fd0f9
Revert "Add ability to filter ConfigDump."
paul-r-gall 34f1993
Add ConfigDumpFilter setup with default filter extension.
paul-r-gall 74606de
Merge remote-tracking branch 'upstream/main' into FilterConfigDump
paul-r-gall 56627a4
Fix PURE virtual fxns
paul-r-gall d2105e5
simple name matching only
paul-r-gall 65ad9a3
Merge remote-tracking branch 'upstream/main' into FilterConfigDump
paul-r-gall 57ec7e4
move universal matcher to common lib
paul-r-gall 30957dd
catch RE2 failure exception
paul-r-gall f51e4de
fix build errors
paul-r-gall 4319328
add testing
paul-r-gall 10252d1
Add documentation
paul-r-gall 52fe34f
fix whitespace issues
paul-r-gall 5741f4d
remove offending log
paul-r-gall 7a8b47f
fix coverage
paul-r-gall f12d0b8
additional coverage fixes
paul-r-gall 2bb4801
Merge remote-tracking branch 'upstream/main' into FilterConfigDump
paul-r-gall 2f92553
fix formatting
paul-r-gall 64a720b
Merge branch 'main' into FilterConfigDump
paul-r-gall 2b7b069
docs and exception fix
paul-r-gall 3c46827
Merge remote-tracking branch 'upstream/main' into FilterConfigDump
paul-r-gall 1e2c4fc
Merge remote-tracking branch 'upstream/main' into FilterConfigDump
paul-r-gall File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doc nit: Can you ref link some example name fields for the user so it's more clear what name we are referring to. Separately, this means that effectively we need a
namefield in all xDS protos to make this consistent, right? (Just trying to make sure I understand.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So currently all xDS protos have a name-like field; most of those name-like fields are actually called
name, except for endpoints, which havecluster_name. Only the protos whose name-like field matches the given regexp will be added to the dump. E.G. putting inname_regex=prefix.*will return routes such thatroute.name()matches, and endpoints such thatendpoint.cluster_name()matches.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup that makes sense. I would just ref link some fields or just list them in a bullet list to be more clear to the user. Right now I think it might not be clear to the user what this will do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done, for some reason clang-format is complaining about this file and
tools/code_format/check_format.py fixisn't making any changes -- do you know what that's about?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, not sure how it would be complaining about the RST file. What is the error? cc @phlax
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wound up forcing with --no-verify, but the error was
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm this sounds like some type of check format regression. cc @phlax to help out.