-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Origin. #15
Comments
we are working on a new version of gnmi server, which will cover this feature. If there is an immediate need for it, we can have an update based on the current version. |
I think albano specifically mentioned the client gnmi_set to support this. |
Got it. |
Sorry, missed this in my inbox. Sam is correct; I was referencing the client in this Issue. Thanks for the work, looking forward to the new version! |
Hi, I have added a pull request to solve this particular issue. Please check this request. |
@larryleguo |
Add support, via flag, for the gNMI Origin in gnmi_set. This will disambiguate the namespace when a vendor utilizes both OpenConfig and rfc7951 (or otherwise vendor-specific) YANG modules.
When sending OpenConfig JSON, the origin key will have a value of "openconfig".
The text was updated successfully, but these errors were encountered: