airflow.providers.google.cloud.transfers.azure_blob_to_gcs

Module Contents

Classes

AzureBlobStorageToGCSOperator

Operator transfers data from Azure Blob Storage to specified bucket in Google Cloud Storage.

class airflow.providers.google.cloud.transfers.azure_blob_to_gcs.AzureBlobStorageToGCSOperator(*, wasb_conn_id='wasb_default', gcp_conn_id='google_cloud_default', blob_name, container_name, bucket_name, object_name, filename, gzip, impersonation_chain=None, **kwargs)[source]

Bases: airflow.models.BaseOperator

Operator transfers data from Azure Blob Storage to specified bucket in Google Cloud Storage.

See also

For more information on how to use this operator, take a look at the guide: Transfer Data from Azure Blob Storage to Google Cloud Storage

Parameters
  • wasb_conn_id – Reference to the wasb connection.

  • gcp_conn_id (str) – The connection ID to use when fetching connection info.

  • blob_name (str) – Name of the blob

  • container_name (str) – Name of the container

  • bucket_name (str) – The bucket to upload to

  • object_name (str) – The object name to set when uploading the file

  • filename (str) – The local file path to the file to be uploaded

  • gzip (bool) – Option to compress local file or file data for upload

  • impersonation_chain (str | Sequence[str] | None) – Optional service account to impersonate using short-term credentials, or chained list of accounts required to get the access_token of the last account in the list, which will be impersonated in the request. If set as a string, the account must grant the originating account the Service Account Token Creator IAM role. If set as a sequence, the identities from the list must grant Service Account Token Creator IAM role to the directly preceding identity, with first account from the list granting this role to the originating account.

template_fields: Sequence[str] = ('blob_name', 'container_name', 'bucket_name', 'object_name', 'filename')[source]
execute(context)[source]

Derive when creating an operator.

Context is the same dictionary used as when rendering jinja templates.

Refer to get_template_context for more context.

Was this entry helpful?