I'm trying to use autorest to generate a PowerShell module from the Genesys Cloud OpenAPI JSON definition. The definition has 115 schema validation errors, so this isn't possible without hand-editing the JSON to correct those.
Example:
error | schema_violation | Schema violation: must have required property 'description' (paths > /api/v2/externalcontacts/contacts/{contactId}/notes/{noteId} > put > responses > 422)
missingProperty: description
In lieu of using autorest, it'd be cool if Genesys could provide info on how it builds the official SDK's, presuming those are built using the same OpenAPI spec that's publicly available here.
The Genesys Cloud Platform API Swagger v2.0 specification is automatically generated from annotations in the server code (java annotations for swagger). If you have requests to fix/update annotations, it is necessary to contact Genesys Customer Care to report this and open a ticket with them (so they can contact and escalate to the appropriate engineering team/service).
The SDK is automatically regenerated and published from the API's definition after each API release. For more information on the build process, see the platform-client-sdk-common project.