RESTCONF RPC operations #66
Merged
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
REST server now handles "POST /restconf/operations/xxxxx" requests to invoke translib.Action API.
Handle "GET /restconf/operations" requests to return available yang rpc
operations. Only json encoded responses are supported - "accept" header
is ignored. Sample output (assuming device supports 2 rpcs):
{
"operations": {
{ "ietf-system:system-restart" : [null] },
{ "foo:bar" : [null] }
}
}
Reference: RFC8040, section 3.3.2
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.
Handle yang rpc operations through RESTCONF operations resource
requests -- "POST /restconf/operations/xxxxx". Here "xxxxx" is the yang
module qualified rpc name (like "ietf-system:system-restart"). Payload
should contain the json encoded rpc input data; or empty if rpc does not
define any input. REST server invokes
translib.ActionAPI to handlethese requests. On success, REST server returns 200 status with json
encoded rpc output data.
Handle "GET /restconf/operations" requests to return available yang rpc
operations. Clients can use this to discover avaiable rpc operations
resources. Sample output (assuming device supports 2 rpcs):
Reference: RFC8040, section 3.3.2