[PLAT-5255] Update openapi and update to latest

[anderssjoblom-vertex]

This is still work in progress. To build this, you need to add the following change to vertex-api/src/universal/api.yml

--- a/src/universal/api.yml
+++ b/src/universal/api.yml
@@ -1030,14 +1030,14 @@ paths:
             schema:
               $ref: "./schemas/CreatePartRequest.yml"
       responses:
-        "201":
+        "200":
           description: Created Part
           content:
             "application/vnd.api+json":
               schema:
-                $ref: "./schemas/Part.yml"
-        "202":
-          $ref: "#/components/responses/Accepted"
+                oneOf:
+                  - $ref: "./schemas/Part.yml"
+                  - $ref: "./schemas/QueuedTranslationJob.yml"
         "400":
           $ref: "#/components/responses/BadRequest"
         "401":
@@ -1651,7 +1651,9 @@ paths:
           content:
             "application/vnd.api+json":
               schema:
-                $ref: "./schemas/QueuedJob.yml"
+                oneOf:
+                  - $ref: "./schemas/QueuedJob.yml"
+                  - $ref: "./schemas/SceneItem.yml"
         "301":
           $ref: "#/components/responses/MovedPermanently"
         "401":

Summary

This updates the API-Client to a major version 1.0.0 since this is a big breaking change.

This is a major update as it upgraded the openapi generator to version 7.11.0. This version will produce all the OneOf and AnyOf classes so there are no manual generation of java classes except one type: metadata values.

The metadata values doesn't have a enum type for the "type" like a "long" or "float" type and that makes the auto-generated source ignore and value for the type. There is a small modification made to the auto generated to match on the type string and also on the values.

Test Plan

Using test and clients using the library.

Release Notes

Not sure how we would indicate the breaking changes.

Possible Regressions

Not know at this point.

[MadisonEhlers-Vertex]

RE> "The metadata values doesn't have a enum type for the "type" like a "long" or "float" type and that makes the auto-generated source ignore and value for the type. There is a small modification made to the auto generated to match on the type string and also on the values."

Why is this only true for metadata types and not all of the other any ofs that we have?

[MadisonEhlers-Vertex]

Looks good to me, if you've tested the anyof mappings to verify those are working.

[MadisonEhlers-Vertex]

Why is it that only the Metadata types are added here? Do we need to maintain all of these AnyOf relationships?

[MadisonEhlers-Vertex]

Why are all of these examples removed. IIRC, these were added so clients could reference these as to how to use the platform with the java client.

[sonarqubecloud]

Quality Gate passed

Issues
3500 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
22.3% Duplication on New Code

See analysis details on SonarQube Cloud