airflow.providers.google.cloud.transfers.sheets_to_gcs

Module Contents

Classes

GoogleSheetsToGCSOperator

Writes Google Sheet data into Google Cloud Storage.

class airflow.providers.google.cloud.transfers.sheets_to_gcs.GoogleSheetsToGCSOperator(*, spreadsheet_id, destination_bucket, sheet_filter=None, destination_path=None, gcp_conn_id='google_cloud_default', impersonation_chain=None, **kwargs)[source]

Bases: airflow.models.BaseOperator

Writes Google Sheet data into Google Cloud Storage.

See also

For more information on how to use this operator, take a look at the guide: Upload data from Google Sheets to GCS

Parameters
  • spreadsheet_id (str) – The Google Sheet ID to interact with.

  • sheet_filter (list[str] | None) – Default to None, if provided, Should be an array of the sheet titles to pull from.

  • destination_bucket (str) – The destination Google cloud storage bucket where the report should be written to. (templated)

  • destination_path (str | None) – The Google cloud storage URI array for the object created by the operator. For example: path/to/my/files.

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

  • impersonation_chain (str | collections.abc.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 (templated).

template_fields: collections.abc.Sequence[str] = ('spreadsheet_id', 'destination_bucket', 'destination_path', 'sheet_filter', 'impersonation_chain')[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?