airflow.providers.google.cloud.operators.life_sciences

Operators that interact with Google Cloud Life Sciences service.

Module Contents

Classes

LifeSciencesRunPipelineOperator

Runs a Life Sciences Pipeline.

class airflow.providers.google.cloud.operators.life_sciences.LifeSciencesRunPipelineOperator(*, body, location, project_id=PROVIDE_PROJECT_ID, gcp_conn_id='google_cloud_default', api_version='v2beta', impersonation_chain=None, **kwargs)[source]

Bases: airflow.providers.google.cloud.operators.cloud_base.GoogleCloudBaseOperator

Runs a Life Sciences Pipeline.

Warning

This operator is deprecated. Consider using Google Cloud Batch Operators instead. The Life Sciences API (beta) will be discontinued on July 8, 2025 in favor of Google Cloud Batch.

See also

For more information on how to use this operator, take a look at the guide: Running a pipeline

Parameters
  • body (dict) – The request body

  • location (str) – The location of the project

  • project_id (str) – ID of the Google Cloud project if None then default project_id is used.

  • gcp_conn_id (str) – The connection ID to use to connect to Google Cloud.

  • api_version (str) – API version used (for example v2beta).

  • 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] = ('body', 'gcp_conn_id', 'api_version', '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?