-
Notifications
You must be signed in to change notification settings - Fork 41
[Apigee] For Keyur #1717
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
base: master
Are you sure you want to change the base?
[Apigee] For Keyur #1717
Conversation
Summary of ChangesHello @gmechali, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces configuration changes to the Apigee proxy setup to enhance handling of potentially large or long-running API requests and responses. It primarily focuses on disabling HTTP compression to ensure consistent data transfer and enabling request/response streaming, alongside increasing I/O timeouts, to support more robust communication with backend services. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request configures Apigee to support streaming, likely for large payloads, by enabling request streaming, increasing timeouts, and adding a policy to disable response compression for the MCP target. While the changes appear to correctly enable streaming, there is a critical issue: the new am-disable-compression policy is not configured for the production environment, which will cause production deployments to fail. Additionally, the newly introduced 5-minute I/O timeout on the proxy endpoint is quite long and could pose a resource exhaustion risk.
| proxies: | ||
| - name: api | ||
| policies: | ||
| - am-disable-compression |
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.
The new policy am-disable-compression is configured for the nonprod environment, but it is missing from the corresponding prod.yaml file. The mcp.template.xml target endpoint, which is used for both environments, now references this policy. This discrepancy will cause deployments to the prod environment to fail due to a missing policy. To fix this, please also add am-disable-compression to the policies list in deploy/apigee/envs/prod.yaml.
| <Properties> | ||
| <Property name="request.streaming.enabled">true</Property> | ||
| <Property name="response.streaming.enabled">true</Property> | ||
| <Property name="io.timeout.millis">300000</Property> |
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.
A 5-minute I/O timeout (300000 ms) is being introduced. While this might be necessary for large streaming transfers, such a long timeout can make the proxy vulnerable to resource exhaustion, for instance through slowloris-type DoS attacks where clients maintain connections for long periods. Please evaluate if this timeout duration is essential. If so, it would be good practice to add an XML comment explaining the reason for this long timeout to aid future maintenance.
No description provided.