NOTE: This class is auto generated by OpenAPI Generator Ref: https://openapi-generator.tech Do not edit the class manually. :param host: Base url :param api_key: Dict to store API key(s). Each entry in the dict specifies an API key. The dict key is the name of the secur
| 30 | } |
| 31 | |
| 32 | class Configuration(object): |
| 33 | """NOTE: This class is auto generated by OpenAPI Generator |
| 34 | |
| 35 | Ref: https://openapi-generator.tech |
| 36 | Do not edit the class manually. |
| 37 | |
| 38 | :param host: Base url |
| 39 | :param api_key: Dict to store API key(s). |
| 40 | Each entry in the dict specifies an API key. |
| 41 | The dict key is the name of the security scheme in the OAS specification. |
| 42 | The dict value is the API key secret. |
| 43 | :param api_key_prefix: Dict to store API prefix (e.g. Bearer) |
| 44 | The dict key is the name of the security scheme in the OAS specification. |
| 45 | The dict value is an API key prefix when generating the auth data. |
| 46 | :param username: Username for HTTP basic authentication |
| 47 | :param password: Password for HTTP basic authentication |
| 48 | :param discard_unknown_keys: Boolean value indicating whether to discard |
| 49 | unknown properties. A server may send a response that includes additional |
| 50 | properties that are not known by the client in the following scenarios: |
| 51 | 1. The OpenAPI document is incomplete, i.e. it does not match the server |
| 52 | implementation. |
| 53 | 2. The client was generated using an older version of the OpenAPI document |
| 54 | and the server has been upgraded since then. |
| 55 | If a schema in the OpenAPI document defines the additionalProperties attribute, |
| 56 | then all undeclared properties received by the server are injected into the |
| 57 | additional properties map. In that case, there are undeclared properties, and |
| 58 | nothing to discard. |
| 59 | :param disabled_client_side_validations (string): Comma-separated list of |
| 60 | JSON schema validation keywords to disable JSON schema structural validation |
| 61 | rules. The following keywords may be specified: multipleOf, maximum, |
| 62 | exclusiveMaximum, minimum, exclusiveMinimum, maxLength, minLength, pattern, |
| 63 | maxItems, minItems. |
| 64 | By default, the validation is performed for data generated locally by the client |
| 65 | and data received from the server, independent of any validation performed by |
| 66 | the server side. If the input data does not satisfy the JSON schema validation |
| 67 | rules specified in the OpenAPI document, an exception is raised. |
| 68 | If disabled_client_side_validations is set, structural validation is |
| 69 | disabled. This can be useful to troubleshoot data validation problem, such as |
| 70 | when the OpenAPI document validation rules do not match the actual API data |
| 71 | received by the server. |
| 72 | :param server_index: Index to servers configuration. |
| 73 | :param server_variables: Mapping with string values to replace variables in |
| 74 | templated server configuration. The validation of enums is performed for |
| 75 | variables with defined enum values before. |
| 76 | :param server_operation_index: Mapping from operation ID to an index to server |
| 77 | configuration. |
| 78 | :param server_operation_variables: Mapping from operation ID to a mapping with |
| 79 | string values to replace variables in templated server configuration. |
| 80 | The validation of enums is performed for variables with defined enum values before. |
| 81 | :param ssl_ca_cert: str - the path to a file of concatenated CA certificates |
| 82 | in PEM format |
| 83 | |
| 84 | :Example: |
| 85 | |
| 86 | API Key Authentication Example. |
| 87 | Given the following security scheme in the OpenAPI specification: |
| 88 | components: |
| 89 | securitySchemes: |
no outgoing calls