PF-1.6: updated default instance type

[sudhirakondi]

Code modificiton to set default instance type for the network-instance.

[OpenConfigBot]

Pull Request Functional Test Report for #5590 / 169dd99

Virtual Devices

Device	Test	Test Documentation	Job	Raw Log
Arista cEOS		PF-1.6: Policy based VRF selection for IPV4/IPV6
Cisco 8000E		PF-1.6: Policy based VRF selection for IPV4/IPV6
Cisco XRd		PF-1.6: Policy based VRF selection for IPV4/IPV6
Juniper ncPTX		PF-1.6: Policy based VRF selection for IPV4/IPV6
Nokia SR Linux		PF-1.6: Policy based VRF selection for IPV4/IPV6
Openconfig Lemming		PF-1.6: Policy based VRF selection for IPV4/IPV6

Hardware Devices

Device	Test	Test Documentation	Raw Log
Arista 7808		PF-1.6: Policy based VRF selection for IPV4/IPV6
Cisco 8808		PF-1.6: Policy based VRF selection for IPV4/IPV6
Juniper PTX10008		PF-1.6: Policy based VRF selection for IPV4/IPV6
Nokia 7250 IXR-10e		PF-1.6: Policy based VRF selection for IPV4/IPV6

Help

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 refactors the network instance configuration flow within the policy-based VRF selection test. By reordering the calls to update the DUT with network instance configurations, the changes ensure that the environment is correctly initialized before BGP services are enabled, improving the reliability of the test setup.

Highlights

• Network Instance Configuration: Updated the configuration sequence for network instances to ensure they are applied to the DUT before enabling BGP.
• Code Cleanup: Removed redundant network instance update calls from the later stages of the configuration function.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the 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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. 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.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request rearranges the configuration sequence for network instances and BGP in the VRF selection test. However, moving the UpdateNetworkInstanceOnDut calls to before the BGP neighbor configuration prevents the in-memory BGP neighbor configurations from being pushed to the DUT. To resolve this, the UpdateNetworkInstanceOnDut calls must also be executed after the BGP neighbors are configured.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.