Removing ETag for getTransportPolicySnapshot api#3221
Removing ETag for getTransportPolicySnapshot api#3221havetisyan merged 1 commit intoAthenZ:masterfrom
Conversation
Summary of ChangesHello, 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 streamlines the Highlights
Changelog
Activity
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
|
Signed-off-by: Sasi Palaka <palakas@yahooinc.com>
There was a problem hiding this comment.
Code Review
This pull request removes ETag support from the getTransportPolicySnapshot API, based on the premise that snapshots are immutable. My review points out that the API definitions seem to allow for snapshot modification (specifically the active status), which would make ETag caching beneficial for performance. I've added a comment requesting clarification on this discrepancy between the stated goal and the API's capabilities.
Description
Removing ETag support for getTransportPolicySnapshot() api since the snapshot doesn't change after it is created.
The earlier api didn't make it into the release, so it is safe to make this change now.
Contribution Checklist:
Attach Screenshots (Optional)