make specification of an operation compliant with RFC8040 section 3.6 #32
Conversation
This file contains 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
an operation is specified by the <module name>:<operation id>. check to make sure that module name and operation ID both match the YANG spec.
|
I needed to make a larger and more specific change for restconf operations GET and PUT, see patch above. |
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.
RFC 8030 section 3.6 indicates that an operation is identified by both module name and operation ID. The latest code used the prefix rather than the module name, which I believe is contrary to the RFC. This pull request removes the (possibly) erroneous check of the prefix and changes the code to require a module name match to resolve #31