-
Notifications
You must be signed in to change notification settings - Fork 2
Add Phase 1 API Gateway improvements #378
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
Open
poyrazK
wants to merge
6
commits into
main
Choose a base branch
from
release/gateway-phase1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+595
−76
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
a2d872b
Add Phase 1 API Gateway improvements: timeouts, TLS, trace headers
poyrazK bd9b5df
Add gateway handler with CIDR check, trace injection, and body limit
poyrazK 0dcac66
Add per-route rate limiting to IPRateLimiter
poyrazK 17e301f
Fix minor issues: logger nil check, error comment, trailing newlines
poyrazK 65af1ad
docs: update swagger docs for API gateway Phase 1 features
poyrazK 183514c
fix(gateway): suppress gosec G402 for intentional TLSSkipVerify
poyrazK 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
Oops, something went wrong.
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.
New optional fields are missing
omitemptyin their JSON tags — coding guidelines violation.All eight new fields are optional (zero/nil means "disabled" or "no restriction") but none carry
omitempty:DialTimeout/ResponseHeaderTimeout/IdleConnTimeoutMaxBodySizeAllowedCIDRs/BlockedCIDRsTLSSkipVerify/RequireTLSfalse)For the
boolfields, note thatomitemptyon a plainboolwill omitfalse, which is fine for GET/serialization semantics here sincefalseis the safe default. If a future update path (e.g. PATCH) needs to explicitly reset a flag tofalseand detect that in a JSON body, the fields would need to be*boolinstead.🔧 Proposed fix
As per coding guidelines: "Include
jsontags on struct fields withomitemptyfor optional fields."📝 Committable suggestion
🤖 Prompt for AI Agents