[NETCONF-1021] OpenAPI: Do not hardcode action path Created: 09/May/23 Updated: 10/Aug/23 Resolved: 10/Aug/23 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-openapi |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0, 4.0.9, 5.0.8, 6.0.2 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Ivan Hrasko | Assignee: | Šimon Ukuš |
| Resolution: | Done | Votes: | 0 |
| Labels: | pt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
Action paths are created in BaseYangOpenApiGenerator by appending rests/operations instead of rests/data. Both sides of this replacing are not configurable. If user (for example lighty.io) uses custom OpenAPI path this can lead to troubles as seen in Hardcoded expected behaviour: rests/data<THE-REST-OF-PATH> -> rests/operations<THE-REST-OF-PATH> Unexpected hardcoded behaviour: restconf/data<THE-REST-OF-PATH> -> rest/operationsata<THE-REST-OF-PATH> |