Conversation
Pull Request Functional Test Report for #5197 / 1d26af5Virtual Devices
Hardware Devices
|
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 introduces a new platform-specific deviation for Cisco devices, acknowledging their current inability to apply Route Policy Language (RPL) policies directly to BGP peer-groups. The change ensures that automated tests correctly account for this behavior by conditionally adjusting expected configurations, thereby improving the accuracy and robustness of network device testing against platform limitations. Highlights
Changelog
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.
Code Review
This pull request introduces the BgpRplDirectlyUnderPeerGroupUnsupported deviation for Cisco devices, which involves updating the proto definition, adding a deviation helper function, enabling it in test metadata, and adjusting local_bgp_test to handle cases where BGP routing policies cannot be directly attached to a peer group. The implementation is consistent with repository standards, and no security vulnerabilities were found.
Adding BgpRplDirectlyUnderPeerGroupUnsupported deviation , since attaching a RPL policy directly under a BGP peer-group is not supported.
RPL config is only supported under AFI/SAFI for a neighbor or peer-group config.
Bug: https://partnerissuetracker.corp.google.com/issues/490033220
this replaces the obsolete older PR #4627 addressing the same issue.