...
In the current implementation, we are using SpringFox to generate teh the Swagger from the Swagger 2 annotations, but SpringFox has many bugs, is not maintained, and uses an old version of SpringBoot, preventing us from upgrading SpringBoot, see
| Jira |
|---|
| server | ONAP Jira |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | POLICY-4142 |
|---|
|
. However, the
SPringfox Springfox annotations are very incompatible with the new OpenAPI Java annotations. Revising the annotations would be a complex task.
...
The current Policy API and Policy PAP interfaces are stable. The issue here is
| Jira |
|---|
| server | ONAP Jira |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | POLICY-41424404 |
|---|
|
, the Swagger is generated by Springfox.
...
- Update the Swagger document in "src/main/resources/openapi/openapi.yaml" to be OpenAPI 3.0 compatible
- Generate the REST interface code from the OpenAPI specifications (See ACM approach below)
- Modify the code to use the generated REST interface code
- Create contract testing stubs for API and PAP
...
