MysqlaasClient

class oci.mysql.MysqlaasClient(config, **kwargs)

The API for the MySQL Database Service

Methods

__init__(config, **kwargs) Creates a new service client
create_configuration(…) Creates a new Configuration.
delete_configuration(configuration_id, **kwargs) Deletes a Configuration.
get_configuration(configuration_id, **kwargs) Get the full details of the specified Configuration, including the list of MySQL Variables and their values.
list_configurations(compartment_id, **kwargs) Lists the Configurations available when creating a DB System.
list_shapes(compartment_id, **kwargs) Gets a list of the shapes you can use to create a new MySQL DB System.
list_versions(compartment_id, **kwargs) Get a list of supported and available MySQL database major versions.
update_configuration(configuration_id, …) Updates the Configuration details.
__init__(config, **kwargs)

Creates a new service client

Parameters:
  • config (dict) – Configuration keys and values as per SDK and Tool Configuration. The from_file() method can be used to load configuration from a file. Alternatively, a dict can be passed. You can validate_config the dict using validate_config()
  • service_endpoint (str) – (optional) The endpoint of the service to call using this client. For example https://iaas.us-ashburn-1.oraclecloud.com. If this keyword argument is not provided then it will be derived using the region in the config parameter. You should only provide this keyword argument if you have an explicit need to specify a service endpoint.
  • timeout (float or tuple(float, float)) – (optional) The connection and read timeouts for the client. The default values are connection timeout 10 seconds and read timeout 60 seconds. This keyword argument can be provided as a single float, in which case the value provided is used for both the read and connection timeouts, or as a tuple of two floats. If a tuple is provided then the first value is used as the connection timeout and the second value as the read timeout.
  • signer (AbstractBaseSigner) –

    (optional) The signer to use when signing requests made by the service client. The default is to use a Signer based on the values provided in the config parameter.

    One use case for this parameter is for Instance Principals authentication by passing an instance of InstancePrincipalsSecurityTokenSigner as the value for this keyword argument

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to all calls made by this service client (i.e. at the client level). There is no retry strategy applied by default. Retry strategies can also be applied at the operation level by passing a retry_strategy keyword argument as part of calling the operation. Any value provided at the operation level will override whatever is specified at the client level.

    This should be one of the strategies available in the retry module. A convenience DEFAULT_RETRY_STRATEGY is also available. The specifics of the default retry strategy are described here.

  • circuit_breaker_strategy (obj) – (optional) A circuit breaker strategy to apply to all calls made by this service client (i.e. at the client level). This client will not have circuit breakers enabled by default, users can use their own circuit breaker strategy or the convenient DEFAULT_CIRCUIT_BREAKER_STRATEGY provided by the SDK to enable it. The specifics of circuit breaker strategy are described here.
  • circuit_breaker_callback (function) – (optional) Callback function to receive any exceptions triggerred by the circuit breaker.
create_configuration(create_configuration_details, **kwargs)

Creates a new Configuration.

Parameters:
  • create_configuration_details (oci.mysql.models.CreateConfigurationDetails) – (required) Request to create a Configuration.
  • opc_request_id (str) – (optional) Customer-defined unique identifier for the request. If you need to contact Oracle about a specific request, please provide the request ID that you supplied in this header with the request.
  • opc_retry_token (str) – (optional) A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type Configuration

Return type:

Response

Example:

Click here to see an example of how to use create_configuration API.

delete_configuration(configuration_id, **kwargs)

Deletes a Configuration. The Configuration must not be in use by any DB Systems.

Parameters:
  • configuration_id (str) – (required) The OCID of the Configuration.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the If-Match header to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Customer-defined unique identifier for the request. If you need to contact Oracle about a specific request, please provide the request ID that you supplied in this header with the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type None

Return type:

Response

Example:

Click here to see an example of how to use delete_configuration API.

get_configuration(configuration_id, **kwargs)

Get the full details of the specified Configuration, including the list of MySQL Variables and their values.

Parameters:
  • configuration_id (str) – (required) The OCID of the Configuration.
  • opc_request_id (str) – (optional) Customer-defined unique identifier for the request. If you need to contact Oracle about a specific request, please provide the request ID that you supplied in this header with the request.
  • if_none_match (str) – (optional) For conditional requests. In the GET call for a resource, set the If-None-Match header to the value of the ETag from a previous GET (or POST or PUT) response for that resource. The server will return with either a 304 Not Modified response if the resource has not changed, or a 200 OK response with the updated representation.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type Configuration

Return type:

Response

Example:

Click here to see an example of how to use get_configuration API.

list_configurations(compartment_id, **kwargs)

Lists the Configurations available when creating a DB System.

This may include DEFAULT configurations per Shape and CUSTOM configurations.

The default sort order is a multi-part sort by:
  • shapeName, ascending
  • DEFAULT-before-CUSTOM
  • displayName ascending
Parameters:
  • compartment_id (str) –

    (required) The compartment OCID.

  • opc_request_id (str) – (optional) Customer-defined unique identifier for the request. If you need to contact Oracle about a specific request, please provide the request ID that you supplied in this header with the request.
  • configuration_id (str) – (optional) The requested Configuration instance.
  • lifecycle_state (str) –

    (optional) Configuration Lifecycle State

    Allowed values are: “ACTIVE”, “DELETED”

  • type (list[str]) –

    (optional) The requested Configuration types.

    Allowed values are: “DEFAULT”, “CUSTOM”

  • display_name (str) – (optional) A filter to return only the resource matching the given display name exactly.
  • shape_name (str) – (optional) The requested Shape name.
  • sort_by (str) –

    (optional) The field to sort by. Only one sort order may be provided. Time fields are default ordered as descending. Display name is default ordered as ascending.

    Allowed values are: “displayName”, “shapeName”, “timeCreated”, “timeUpdated”

  • sort_order (str) –

    (optional) The sort order to use (ASC or DESC).

    Allowed values are: “ASC”, “DESC”

  • limit (int) –

    (optional) The maximum number of items to return in a paginated list call. For information about pagination, see List Pagination.

  • page (str) –

    (optional) The value of the opc-next-page or opc-prev-page response header from the previous list call. For information about pagination, see List Pagination.

  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of ConfigurationSummary

Return type:

Response

Example:

Click here to see an example of how to use list_configurations API.

list_shapes(compartment_id, **kwargs)

Gets a list of the shapes you can use to create a new MySQL DB System. The shape determines the resources allocated to the DB System: CPU cores and memory for VM shapes; CPU cores, memory and storage for non-VM (or bare metal) shapes.

Parameters:
  • compartment_id (str) –

    (required) The compartment OCID.

  • opc_request_id (str) – (optional) Customer-defined unique identifier for the request. If you need to contact Oracle about a specific request, please provide the request ID that you supplied in this header with the request.
  • is_supported_for (list[str]) –

    (optional) Return shapes that are supported by the service feature.

    Allowed values are: “DBSYSTEM”, “ANALYTICSCLUSTER”, “HEATWAVECLUSTER”

  • availability_domain (str) – (optional) The name of the Availability Domain.
  • name (str) – (optional) Name
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of ShapeSummary

Return type:

Response

Example:

Click here to see an example of how to use list_shapes API.

list_versions(compartment_id, **kwargs)

Get a list of supported and available MySQL database major versions.

The list is sorted by version family.

Parameters:
  • compartment_id (str) –

    (required) The compartment OCID.

  • opc_request_id (str) – (optional) Customer-defined unique identifier for the request. If you need to contact Oracle about a specific request, please provide the request ID that you supplied in this header with the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type list of VersionSummary

Return type:

Response

Example:

Click here to see an example of how to use list_versions API.

update_configuration(configuration_id, update_configuration_details, **kwargs)

Updates the Configuration details.

Parameters:
  • configuration_id (str) – (required) The OCID of the Configuration.
  • update_configuration_details (oci.mysql.models.UpdateConfigurationDetails) – (required) Request to update a Configuration.
  • if_match (str) – (optional) For optimistic concurrency control. In the PUT or DELETE call for a resource, set the If-Match header to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource’s current etag value.
  • opc_request_id (str) – (optional) Customer-defined unique identifier for the request. If you need to contact Oracle about a specific request, please provide the request ID that you supplied in this header with the request.
  • retry_strategy (obj) –

    (optional) A retry strategy to apply to this specific operation/call. This will override any retry strategy set at the client-level.

    This should be one of the strategies available in the retry module. This operation will not retry by default, users can also use the convenient DEFAULT_RETRY_STRATEGY provided by the SDK to enable retries for it. The specifics of the default retry strategy are described here.

    To have this operation explicitly not perform any retries, pass an instance of NoneRetryStrategy.

Returns:

A Response object with data of type Configuration

Return type:

Response

Example:

Click here to see an example of how to use update_configuration API.