Google Cloud RunTransferConfig

Google Cloud RunTransferConfig

Certified

Trigger a BigQuery Data Transfer Service run

Starts a manual run of an existing BigQuery Data Transfer Service transfer config, or re-attaches to a run that is already pending or running for that config so a retried execution never starts a duplicate run. Optionally polls the run until it reaches a terminal state, on a wall-clock deadline.

yaml
type: io.kestra.plugin.gcp.bigquery.RunTransferConfig

Trigger a scheduled query transfer config and wait for it to complete.

yaml
id: bigquery_data_transfer
namespace: company.team

tasks:
  - id: trigger_transfer
    type: io.kestra.plugin.gcp.bigquery.RunTransferConfig
    projectId: "{{ secret('GCP_PROJECT_ID') }}"
    transferConfigName: projects/my-project/locations/us/transferConfigs/615123456789012345
    pollInterval: PT15S
    maxDuration: PT1H
    # Enterprise Edition: emit the destination as a data-lineage asset.
    assets:
      enableAuto: true
Properties

The transfer config resource name

Format: projects/{project}/locations/{location}/transferConfigs/{config}.

Assets this task consumes as inputs or produces as outputs, for lineage tracking and the asset graph (Enterprise Edition). A flow declaring this property on a task is rejected in the open-source edition.

Definitions
assetFailureBehaviorstring
Possible Values
IGNOREFAILWARN

Asset failure behavior

Behavior applied to the task state when a declared asset fails to render, emit, or be persisted (e.g. a lock conflict): FAIL escalates it to FAILED, WARN (default) warns it if it would otherwise succeed, IGNORE leaves the state untouched.

enableAutobooleanstring

Whether to auto-register assets referenced dynamically at runtime that are not statically declared in inputs or outputs.

inputsarray

The assets consumed as inputs.

id*string
Min length1
typestring
outputs

The assets produced as outputs.

id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*object
descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150
id*string
Min length1
Max length150
type*string
Min length1

Custom asset type

descriptionstring
displayNamestring
metadataobject
Default{}
namespacestring
Min length1
Max length150

The GCP service account to impersonate

DefaultPT1H

The maximum duration to wait before timing out, used only when wait is true

DefaultPT15S

The interval between polls, used only when wait is true

The GCP project ID

Defaulttrue

Whether to re-attach to an already pending or running run of this config instead of starting a new one

When true (default), the task first looks for a run of this config that is already pending or running and adopts it, so a retried execution never starts a duplicate run. A pending run whose schedule time is in the future is never adopted: it is queued, not in-flight. A running run is always in-flight and stays eligible whatever its schedule time. This matters for transfers with a refresh window (Google Ads, GA4, YouTube), where Google permanently keeps a chain of pending runs queued ahead of now, one per backfill date. By default any in-flight run is adopted regardless of its age; set reattachMaxAge to opt into treating an old in-flight run as stale so a fresh run is started instead. Set to false to always start a new run.

The maximum age of an in-flight run that can still be re-attached to

Used only when reattach is true. When set, an in-flight (pending or running) run whose schedule time is older than now - reattachMaxAge is treated as stale and is NOT adopted -- a fresh run is started instead. When unset (default), any in-flight run is adopted regardless of its age. This is independent of maxDuration, which only bounds how long this task waits for a run to reach a terminal state.

SubTypestring
Default["https://www.googleapis.com/auth/cloud-platform"]

The GCP scopes to be used

The GCP service account

Defaulttrue

Whether to wait until the transfer run reaches a terminal state

When false, the task returns as soon as the run is triggered and does not emit a destination asset, since completion is not confirmed.

The destination dataset ID of the transfer config

The location, parsed from the transfer config resource name

The GCP project ID, parsed from the transfer config resource name

Defaultfalse

Whether an existing in-flight run was re-attached instead of starting a new one

The full resource name of the transfer run

The state of the transfer run, terminal when wait is true

The wall-clock time spent waiting for the transfer run to reach a terminal state, recorded only when wait is true.

Whether the task re-attached to an already in-flight transfer run (1) or started a new one (0).