Release v0.8.0 · openconfig/ygnmi

Backwards-incompatible Changes

ygnmi now supports telemetry-atomic nodes by avoiding generation of child paths below them.
ordered-by user lists are supported via generating a custom Go struct satisfying the ygot.GoOrderedMap interface (this is introduced by [email protected]). Note that ordered-by user lists are assumed to be telemetry-atomic, and thus elements below are not directly accessible. The reason is that the current gnmi reference implementation does not support both ordered data retrieval and finer-grained retrieval at the same time.

All OpenConfig-style compressed lists now have a Path().To().ListNameMap() method that returns the ygot map type. It is now possible to directly query for the whole list, or do a replace/update/delete on a whole list.

add baseQuery for common things between leaf and non-leaf Query objects by @wenovus in #94
Generate extras/plugin at same time as child constructors. by @wenovus in #95
Unify leaf/non-leaf query structs into a single struct. by @wenovus in #99
Path generation for ygot.OrderedMap nodes by @wenovus in #96
Generate CompressionInfo for OrderedMap PathStructs by @wenovus in #97
Ordered Map helper support by @wenovus in #98
Proposal: Generate Map method for all keyed lists. by @wenovus in #100
Generate "Map" PathStructs and gNMI helpers by @wenovus in #101
Add integration tests for map PathStruct gNMI helpers by @wenovus in #102
Add hidden flag to not generate ordered maps by @wenovus in #103
generate_ordered_map -> generate_atomic_lists by @wenovus in #104
Remove unused test func to fix lint by @wenovus in #105

Full Changelog: v0.7.10...v0.8.0