You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Side Note: Below bug report based on GET request, but this case also applies to DELETE
Actual behavior
In the case of the Yang node request with multiple key values, restconf server response contains only resource coupled with the first key.
Considering the following request GET .../<list_node>=<key_1>,<key_2>,...,<key_n>
Server responds with: {<key_1_resource_value>}
Expected behavior
In the case of the Yang node request with multiple key values, restconf server response contains all resources coupled with each requested key.
Considering the following request GET .../<list_node>=<key_1>,<key_2>,...,<key_n>
Server responds with: {<key_1_resource_value>, <key_2_resource_value>,...,<key_n_resource_value>}
Reproduction steps Code used to reproduce the bug can be found in the section below
Start restconf server - go run main.go
Create more than 1 resource within the books Yang node (it is already done, by configuration within startup.json file)
Perform read request, requesting more than 1 resource from the books list-node
Request: curl -X GET http://localhost:8080/restconf/data/library:books=0,1
Response: {"book-id":0,"title":"Book nr 0"}
Code used to reproduce a bug yang/library.yang
module library {
revision2024-10-03;
list books {
key book-id;
leaf book-id {
description"unique id for book";
typeint32;
}
leaf title {
description"title of the book";
typestring;
}
}
}
The text was updated successfully, but these errors were encountered:
Pawel-Guzik
changed the title
restconf server does NOT support multiple keys GET request, on list node.
restconf server does NOT support multiple keys GET request on list nodes.
Oct 3, 2024
Pawel-Guzik
changed the title
restconf server does NOT support multiple keys GET request on list nodes.
Restconf server does NOT support multiple keys GET request on list nodes.
Oct 3, 2024
Pawel-Guzik
changed the title
Restconf server does NOT support multiple keys GET request on list nodes.
Restconf server does NOT support multiple keys request on list nodes.
Oct 3, 2024
Pawel-Guzik
changed the title
Restconf server does NOT support multiple keys request on list nodes.
Restconf server does NOT support multiple keys requests on list nodes.
Oct 3, 2024
Pawel-Guzik
changed the title
Restconf server does NOT support multiple keys requests on list nodes.
Restconf server does NOT support multiple key requests on list nodes.
Oct 3, 2024
Side Note: Below bug report based on
GET
request, but this case also applies toDELETE
Actual behavior
In the case of the Yang node request with multiple key values, restconf server response contains only resource coupled with the first key.
GET .../<list_node>=<key_1>,<key_2>,...,<key_n>
{<key_1_resource_value>}
Expected behavior
In the case of the Yang node request with multiple key values, restconf server response contains all resources coupled with each requested key.
GET .../<list_node>=<key_1>,<key_2>,...,<key_n>
{<key_1_resource_value>, <key_2_resource_value>,...,<key_n_resource_value>}
Reproduction steps
Code used to reproduce the bug can be found in the section below
go run main.go
books
Yang node (it is already done, by configuration withinstartup.json
file)books
list-nodeRequest:
curl -X GET http://localhost:8080/restconf/data/library:books=0,1
Response:
{"book-id":0,"title":"Book nr 0"}
Code used to reproduce a bug
yang/library.yang
main.go
startup.json
Additional informations
Related RESTCONF rfc section - https://datatracker.ietf.org/doc/html/rfc8040#section-3.5.3
go.mod
content:The text was updated successfully, but these errors were encountered: