MySQL Shell API 9.2.0
Unified development interface for MySQL Products
|
If the osBucketName option is used, the specified OCI bucket is used as the file storage. Connection is established using the local OCI configuration file. The directory structure is simulated within the object name.
The osNamespace, ociConfigFile, ociProfile and ociAuth options cannot be used if the osBucketName option is not set or set to an empty string.
The osNamespace option overrides the OCI namespace obtained based on the tenancy ID from the local OCI profile.
The ociAuth option allows to specify the authentication method used when connecting to the OCI:
For more information please see: https://docs.oracle.com/en-us/iaas/Content/API/Concepts/sdk_authentication_methods.htm
When using a PAR to perform an operation, the OCI configuration is not needed to execute it (the osBucketName option should not be set).
When using PAR to a specific file, the generated PAR URL should be used as argument for an operation. The following is a file PAR to export a table to 'tab.tsv' file at the 'dump' directory of the 'test' bucket:
When using a bucket PAR, the generated PAR URL should be used as argument for an operation. The following is a bucket PAR to create a dump at the root directory of the 'test' bucket:
When using a prefix PAR, argument should contain the PAR URL itself and the prefix used to generate it. The following is a prefix PAR to create a dump at the 'dump' directory of the 'test' bucket. The PAR was created using 'dump' as prefix:
Note that the prefix PAR URL must end with a slash, because otherwise it will be treated as a PAR to specific file.
Reading from a PAR to specific file
The following access type is required to read from such PAR:
Reading from a bucket or a prefix PAR
The following access types are required to read from such PAR:
Writing to a PAR to specific file
The following access type is required to write to such PAR:
Writing to a bucket or a prefix PAR
The following access types are required to write to such PAR:
Note that read access is required in this case, because otherwise it is not possible to list the objects.
If the s3BucketName option is used, the specified AWS S3 bucket is used as the file storage. Connection is established using default local AWS configuration paths and profiles, unless overridden. The directory structure is simulated within the object name.
The s3CredentialsFile, s3ConfigFile, s3Profile, s3Region and s3EndpointOverride options cannot be used if the s3BucketName option is not set or set to an empty string.
All failed connections to AWS S3 are retried three times, with a 1 second delay between retries. If a failure occurs 10 minutes after the connection was created, the delay is changed to an exponential back-off strategy:
Handling of the AWS settings
The AWS options are evaluated in the order of precedence, the first available value is used.
The AWS credentials are fetched from the following providers, in the order of precedence:
The items specified above correspond to the following credentials:
Role is assumed using the following settings from the AWS config file:
The multi-factor authentication is not supported. For more information on assuming a role, please consult the AWS documentation.
The process/command line specified by the credential_process setting must write a JSON object to the standard output in the following form:
The Amazon ECS credentials are fetched from a URI specified by an environment variable AWS_CONTAINER_CREDENTIALS_RELATIVE_URI (its value is appended to 'http://169.254.170.2'). If this environment variable is not set, the value of AWS_CONTAINER_CREDENTIALS_FULL_URI environment variable is used instead. If neither of these environment variables are set, ECS credentials are not used.
The request may optionally be sent with an 'Authorization' header. If the AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE environment variable is set, its value should specify an absolute file path to a file that contains the authorization token. Alternatively, the AWS_CONTAINER_AUTHORIZATION_TOKEN environment variable should be used to explicilty specify that authorization token. If neither of these environment variables are set, the 'Authorization' header is not sent with the request.
The reply is expected to be a JSON object in the following form:
The Amazon IMDS credential provider is configured using the following environment variables:
and the following settings from the AWS config file:
For more information on IMDS, please consult the AWS documentation.
The Expiration value, if given, specifies when the credentials are going to expire, they will be automatically refreshed before this happens.
The following credential handling rules apply:
If the azureContainerName option is used, the specified Azure container is used as the file storage. Connection is established using the configuration at the local Azure configuration file. The directory structure is simulated within the blob name.
The azureConfigFile, azureStorageAccount and azureStorageSasToken options cannot be used if the azureContainerName option is not set or set to an empty string.
Handling of the Azure settings
The following settings are read from the storage section in the config file:
Additionally, the connection options may be defined using the standard Azure environment variables:
The Azure configuration values are evaluated in the following precedence:
If a connection string is defined either case in the environment variable or the configuration option, the individual configuration values for account and key will be ignored.
If a SAS Token is defined, it will be used for the authorization (ignoring any defined account key).
The default Azure Blob Endpoint to be used in the operations is defined by:
unless a different endpoint is defined in the connection string.