Change generators - Githubissues

displague commented 3 years ago

Use https://github.com/openapi-generators/openapi-python-client/ for modern Python (requires OAS3)

displague commented 3 years ago

Generating metal-python
Warning(s) encountered while generating. Client was generated, but some pieces may be missing

WARNING parsing DELETE /user/api-keys/{id} within authentication.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /api-keys/{id} within authentication.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /projects/{id}/bgp-configs within projects.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing GET /projects/{id}/customdata within projects.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing GET /projects/{project_id}/ips/{id}/customdata within projects.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing DELETE /projects/{id} within projects.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /batches/{id} within batches.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /devices/{id}/actions within devices.

Cannot parse response for status code 202, response will be ommitted from generated client

Response(description='accepted', headers=None, content={}, links=None)

WARNING parsing DELETE /devices/{id} within devices.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing GET /devices/{id}/bandwidth within devices.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing GET /devices/{id}/customdata within devices.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing GET /devices/{instance_id}/ips/{id}/customdata within devices.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing GET /devices/{id}/traffic within devices.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing PUT /bgp/sessions/{id} within bgp.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing DELETE /bgp/sessions/{id} within bgp.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing GET /incidents within incidents.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing GET /organizations/{id}/customdata within organizations.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing DELETE /organizations/{id} within organizations.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /invitations/{id} within invitations.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /ips/{id} within ip_addresses.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing GET /ips/{id}/customdata within ip_addresses.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing DELETE /licenses/{id} within licenses.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /memberships/{id} within memberships.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing GET /users/{id}/customdata within users.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing GET /storage/{id}/customdata within volumes.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing DELETE /storage/attachments/{id} within volumes.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /storage/{volume_id}/snapshots/{id} within volumes.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /storage/snapshot-policies/{id} within volumes.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /storage/{id} within volumes.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /user/otp/verify/{otp} within otps.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /user/otp/sms/receive within otps.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /reset-password within password_reset_tokens.

Cannot parse response for status code 201, response will be ommitted from generated client

Response(description='created', headers=None, content={}, links=None)

WARNING parsing DELETE /payment-methods/{id} within payment_methods.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /spot-market-requests/{id} within spot_market_request.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /ssh-keys/{id} within ssh_keys.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /support-requests within support_request.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /user/otp/app within two_factor_auth.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing DELETE /user/otp/app within two_factor_auth.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /user/otp/sms within two_factor_auth.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing DELETE /user/otp/sms within two_factor_auth.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing PUT /transfers/{id} within transfer_requests.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /transfers/{id} within transfer_requests.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing POST /userdata/validate within userdata.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing PUT /verify-email within user_verification_tokens.

Cannot parse response for status code 200, response will be ommitted from generated client

Response(description='ok', headers=None, content={}, links=None)

WARNING parsing POST /verify-email within user_verification_tokens.

Cannot parse response for status code 201, response will be ommitted from generated client

Response(description='created', headers=None, content={}, links=None)

WARNING parsing DELETE /metal-gateways/{id} within metal_gateways.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

WARNING parsing DELETE /emails/{id} within emails.

Cannot parse response for status code 204, response will be ommitted from generated client

Response(description='no content', headers=None, content={}, links=None)

If you believe this was a mistake or this tool is missing a feature you need, please open an issue at https://github.com/triaxtec/openapi-python-client/issues/new/choose

displague commented 1 year ago

Current warning output is:

$ make 2>&1 | grep WARN | sort | uniq -c
   1 [main] WARN  o.o.c.l.AbstractPythonCodegen - From (reserved word) cannot be used as model name. Renamed to ModelFrom
 177 [main] WARN  o.o.c.l.AbstractPythonCodegen - Type null not handled properly in toExampleValue
   3 [main] WARN  o.o.codegen.DefaultCodegen - Unknown `format` decimal detected for type `number`. Defaulting to `number`
  27 [main] WARN  o.o.codegen.DefaultCodegen - Unknown `format` integer detected for type `number`. Defaulting to `number`
   1 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Facility
   1 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: FacilityInput
   2 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Href
   1 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: InstancesBatchCreateInput_batches_inner_allOf
   4 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Metro
   1 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: MetroInput
   1 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: Project
   1 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: User
   1 [main] WARN  o.o.codegen.DefaultCodegen - allOf with multiple schemas defined. Using only the first one: UserLite

displague commented 1 year ago

$ pipx install openapi-python-client --include-deps
$ pipx upgrade openapi-python-client
$ openapi-python-client generate --path patched.openapi.yaml
Generating metal-api-client
Error(s) encountered while generating, client was not created

WARNING parsing POST /projects/{id}/devices/batch within batches. Endpoint will not be generated.

Could not find reference in parsed models or enums

Reference(ref='#/components/schemas/InstancesBatchCreateInput')

Unable to process schema /components/schemas/InstancesBatchCreateInput_batches_inner:

Cannot take allOf a non-object

Failure to process schema has resulted in the removal of:
/components/schemas/InstancesBatchCreateInput_batches_inner
/components/schemas/InstancesBatchCreateInput

displague / metal-python

Change generators #1