-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Support for space in gnmi path #15405
Comments
Hi, The error comes from the gnxi library we use, which checks the node name against a regex. As the code comment states, hat regex comes from RFC 6020 which states:
Note, spaces or whitespace are not included in this. There is a discussion about whitespace and escaping right before this section in 6.1.3. @srebhan will ask upstream for confirmation as to the support of whitespace. |
@dangleminh I asked for clarification of the standard in openconfig/reference#209, let's wait for an answer and then see how we continue... |
steering away from this convo a bit but any reason why you cannot use the EOS native + the OpenConfig paths to read the same info, for instance EOS version information is stored in
serial number can be found in OC in HTH! |
Just wanted to add on here, as I am running into the same issue, however, there doesn't appear to be a eos_native or openconfig spec on the information I need.
Output:
But I am receiving a similar error:
|
@josh-silvas you are running a |
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Forums or provide additional details in this issue and reqeust that it be re-opened. Thank you! |
Use Case
We are using gnmi input but seems space doesnt work for path, please see below:
Getting the error:
Expected behavior
path is required space as every cli in the network OS contains space. Openconfig gnmic can support space as below:
Actual behavior
Openconfig gnmic can support space as below:
Additional info
No response
The text was updated successfully, but these errors were encountered: