Kerry Meyer

The error message shown here indicates a problem in the software configuration on the server. The 2.4.0 version of this collection works with no problems running the specified playbook against...

No response or additional information has been posted on this Issue since the posting of a demonstration that the functionality (playbook) described works correctly for the specified version of the...

Please make the changes requested by Arun and also make the changes needed to fix the flagged sanity errors.

I'm attempting to clear the failing "changelog" check for this PR (already labeled as a "new_resource_module") by closing and re-opening the PR.

Closing and re-opening to clear "failure" for a missing fragment file.

To proceed with the code review for this resource module, please push changes for the following items: - Re-sync your fork and branch to pull in updates from the "main"...

Thank you for letting us know about this problem. We are looking into it and will get back to you with the result of our analysis and our plan for...

We will update our sonic_bgp_af resource module to add support for the "aggregate-address" configuration option.

Instead of using the "sonic REST" path shown above, we are implementing this feature using the corresponding Openconfig path: Example: path: /openconfig-network-instance:network-instances/network-instance[name=Vrf1]/protocols/protocol[identifier=BGP][name=bgp]/bgp/global/afi-safis/afi-safi[afi-safi-name=IPV6_UNICAST]/aggregate-address-config payload ={"aggregate-address-config": {"aggregate-address": [{"prefix": "2a00:12e8::/60", "config": {"prefix": "2a00:12e8::/60"}}]}}

This request has been fulfilled by the merging of [Add aggregate address configuration support to BGP AF module #398](https://github.com/ansible-collections/dellemc.enterprise_sonic/pull/398).