add capability for keyed paths#39
Merged
LarsxGitHub merged 1 commit intoopenconfig:mainfrom Mar 10, 2026
Merged
Conversation
alshabib
approved these changes
Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR extends CLIO with support for keyed gNMI paths. The idea is to leverage the Metric attributes to encode the keys in PathElem maps as
<PathElemName><attrSep><PathElemMapKey>, e.g.,interface.nameand then copy over the respective value.On the telemetry-generating side this looks as follows:
which translates to the following gNMI path:
Notably, to stay consistent with the existing code the following two caveats apply:
(1) if the update path starts with "container", that PathElem is skipped (as "container" is assumed to be in the prefix)
(2) If an attribute can not be matched, it is assigned to the last PathElem