[NETCONF-708] Swagger generates invalid RFC8040 paths for lists with multiple keys

Wed, 16 Jun 2021 19:46:21 +0000

Getting 500 server error for this rest api using RFC8040 url in swagger which is working perfectly fine with restconf(original) url. Both the urls are mentioned below.

Orignal Url:-http://<Controller IP>:8181+/restconf/config/openconfig-network-instance:network-instances/network-instance/global-bgp/openconfig-network-instance:protocols/protocol/openconfig-policy-types:BGP/bgp-example/bgp/neighbors/neighbor/192.0.2.1/afi-safis/afi-safi/openconfig-bgp-types:IPV4%2DUNICAST
RFC8040 Url:-http://<Controller IP>:8181/rests/data/openconfig-network-instance:network-instances/network-instance=global-bgp/protocols/protocol=openconfig-policy-types%3ABGP=bgp-example/bgp-openconfig-extensions:bgp/neighbors/neighbor=192.0.2.1/afi-safis/afi-safi=openconfig-bgp-types%3AIPV4-UNICAST

In this url, protocol key has two values:
1. Identifier: openconfig-policy-types:BGP 2. Name: bgp-example

According to RFC8040, the multiple keys should be separated with ',' instead of '='.

Valid RFC8040 Url:- http://<Controller IP>:8181/rests/data/openconfig-network-instance:network-instances/network-instance=global-bgp/protocols/protocol=openconfig-policy-types%3ABGP,bgp-example/bgp-openconfig-extensions:bgp/neighbors/neighbor=192.0.2.1/afi-safis/afi-safi=openconfig-bgp-types%3AIPV4-UNICAST

But It is not working even changing '=' with ',' . It seems there is a bug in calling the apis when we have a list of multiple keys(openconfig-policy-types:BGP and bgp-example in above case).

OpenDaylight JIRA

[NETCONF-708] Swagger generates invalid RFC8040 paths for lists with multiple keys