Closed damianoneill closed 5 years ago
@bzeuner Is there any update on this?
Hallo @damianoneill, I cannot really help here and would like to point you to @karthik-sethuraman
Hi, You are correct and it is fixed now by #320. Currently there is no plan to release further 2.0.x versions, but for the next TAPI release 2.1, we are planning to use updated RESTConf mapping, which should not have this issue.
The definition published here https://github.com/OpenNetworkingFoundation/TAPI/blob/develop/SWAGGER/tapi-connectivity%402018-02-16.swagger
is invalid json, this can be confirmed as follows:
The issue is that ine 16986 is a duplicate of 16985, removing 16985 makes it valid.