I checked the rest of the warnings, they all complain about the same thing(operationIds not unique, path parameter missing in POST definition). They all happen in the AbstractDaoRestServiceWithDTO.java . Like I mentioned in the above comment, this is due to our older code structure that mix Rest API code with business logic code. To fix this, we need to refactor the design of this part of the code which seems out of the scope at the point. I think the new API server that we are planning to work on already has a plan to handle Swagger/OpenAPI stuff properly base on the 2 hours Rest API intro session on Tuesday last week.

. No. I only fixed the "version" part. There are still many other warnings that we can't do anything about it right now because most of the OpenAPI doc are auto-generated from our existing RESTful API code written years ago. To solve this completely, we need to refactor the structure of our older code to add annotation to it. But obviously, the team doesn't have plan to do this for now because this will include much effort to test all v2 restful API. All newer RESTful API code written this year has OpenAPI annotation. I'll spend some time next sprint to check if there is anywhere else that we can add annotation without changing the original code to at least reduce some numbers of the warning, then we can close this Jira.

Pull request for adding "version" to "info" section.

https://github.com/OpenNMS/opennms/pull/3484

Initially I had tried importing into Postman, and that failed. The message in the ticket came from https://apitools.dev/swagger-parser/online/