-
Notifications
You must be signed in to change notification settings - Fork 77
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
Backport PR #2636 to release/v1.7 for Bugfix ingress route settings #2642
Merged
Merged
Changes from all commits
Commits
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 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.
💡 Codebase verification
Action Required: Inconsistent Use of Trailing Slashes in Paths
The analysis of the routing configuration reveals inconsistencies in the use of trailing slashes in path definitions. This may lead to unexpected routing behaviors and should be standardized to align with your API design.
Affected Lines:
Lines with trailing slashes:
/vald.v1.Search/
(Lines: 69, 150, 217)/vald.v1.Insert/
(Lines: 75, 156, 223)/vald.v1.Update/
(Lines: 88, 162, 236)/vald.v1.Upsert/
(Lines: 94, 168, 242)/vald.v1.Remove/
(Lines: 100, 174, 248)/vald.v1.Index/
(Lines: 124, 180, 260)/vald.v1.Flush/
(Lines: 131, 267, 273)/vald.v1.Filter/
(Lines: 143, 210, 280)Paths without trailing slashes:
/vald.v1.Update/UpdateTimestamp
(Lines: 82, 230)/vald.v1.Object/Exists
(Lines: 106, 186)/vald.v1.Object/GetTimestamp
(Lines: 112, 192)/vald.v1.Object/
(Lines: 118, 198, 254)/mirror.v1.Mirror/Register
(Lines: 137, 273)/grpc.reflection.v1alpha.ServerReflection/ServerReflectionInfo
(Line: 288)/grpc.reflection.v1.ServerReflection/ServerReflectionInfo
(Line: 302)/
(Line: 280)Recommendations:
Analysis chain
LGTM: Improved routing configuration
The routing configuration has been significantly enhanced to provide more specific routing based on the enabled components (mirror, filter, and LB). This aligns well with the PR objectives.
However, there are a couple of points to consider:
Some routes are marked for future changes (e.g., lines 81-82 and 130-131). It would be beneficial to create follow-up tasks to implement these changes.
The use of trailing slashes in paths (e.g., "/vald.v1.Search/") might affect routing behavior. Ensure that this is the intended configuration and is consistent with your API design.
To verify the consistency of trailing slashes in paths, you can run the following command:
This will list all path definitions, allowing you to review the consistency of trailing slash usage.
Scripts executed
The following scripts were executed for the analysis:
Script:
Length of output: 1587