We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Consider the below config
cli: cfg> show config { "data": { "onfig:forwarding-options": { "class-of-service": { "interface": [ { "name": "ifp-0/0/3", "egress-header-compensation": { "bytes": 40 } } ] } } } }
Now I do the following to delete.
cli: cfg> delete forwarding-options class-of-service interface ifp-0/0/3 egress-header-compensation bytes 32 cli: cfg> show diff name ifp-0/0/3; - egress-header-compensation { - bytes 40; - } }
So irrespective of the value input to the delete , the deletion operation succeeds. The same also is applicable for show config.
cli: cfg> show config forwarding-options class-of-service interface ifp-0/0/3 egress-header-compensation bytes 34 { "config:bytes": 40 }
This will confuse the user, wouldn't throwing an error in case of a wrong input be a better option ?
The text was updated successfully, but these errors were encountered:
Note that this is not the case when input is a string, I have observed this with numerical values.
Sorry, something went wrong.
* [Delete and show config are oblivious to the leaf value #157](#157)
2b820e1
* Added equality of values necessary condition in edit-config delete/remove of leafs
Should be fixed by above commit. Please verify.
Thanks for fixing !
No branches or pull requests
Consider the below config
Now I do the following to delete.
So irrespective of the value input to the delete , the deletion operation succeeds.
The same also is applicable for show config.
This will confuse the user, wouldn't throwing an error in case of a wrong input be a better option ?
The text was updated successfully, but these errors were encountered: