Rob Shakir

Hi Adam, We'll take an action to write a companion document for this, or add it to the descriptions as you suggest. We expect that the neighbour-level configuration overloads the...

You cannot do this with `compress_paths=true`, since this expects the OpenConfig style guide rules to be met (including no duplicate names at the root). Using `compress_paths=false` (the default) will allow...

hi! Apologies for the delay getting back to you. This sounds an interesting use case. Our goal with the IR was to create something that exactly allowed this kind of...

Today, there's not such an option -- it should be possible to write such a function that does the opposite of `PruneConfigFalse` as you note. To do this as an...

Thanks for this test case -- it looks to cover the `Certz` tests explained. I have a few questions and Go implementation comments.

/gcbrun

Apologies, will get to this within the next week or so.

w.r.t `next-hop-groups` -- the general benefit of these is if we end up with lots of sharing. I don't see that we necessarily must have the same approach between AFT...

For reference: * Cisco XR -- allows multiple `path` statements [docs](https://www.cisco.com/c/en/us/td/docs/iosxr/cisco8000/mpls/79x/b-mpls-cg-cisco8000-79x/implementing-mpls-static-labeling.html) * JUNOS -- allows one next-hop, multiple LSPs possible to the same destination using different "name" [docs](https://www.juniper.net/documentation/us/en/software/junos/cli-reference/topics/ref/statement/static-label-switched-path-edit-protocols-mpls.html) - this...

`ygot` is failing here because after path compression we have duplicate names -- i.e., `next-hops/next-hop` and `state/next-hop` are duplicate names in this generated code. Can we select different naming?