sincecutoff.com
← all changes

bq transfer configs support Dataplex Entry Group integration and filtering

Introduced 2026-10-13 · score 0.97

HOW TO USE IT

When creating or updating a transfer config for Dataplex Entry Group integration, use `--dataplex_entry_group`; to list configs with Dataplex configuration metadata, filter with `--filter="metadata_destination.dataplex_configuration:*"`.

bq mk --transfer_config --data_source=<DATA_SOURCE> --dataplex_entry_group=<ENTRY_GROUP>
bq update --transfer_config --dataplex_entry_group=<ENTRY_GROUP> <TRANSFER_CONFIG>
bq ls --transfer_config --transfer_location=<LOCATION> --project_id=<PROJECT_ID> --filter="metadata_destination.dataplex_configuration:*"

WHY THIS HELPS

Create, update, or list transfer configs associated with Dataplex Entry Groups.

REQUIREMENTS AND LIMITATIONS

  • --dataplex_entry_group: Release note says this flag enables Dataplex Entry Group integration for create and update; its value format and requiredness are not documented in the CLI reference.
  • --data_source (required): Data source for the transfer configuration.
  • --transfer_config (required): Selects transfer configuration creation, update, or listing, depending on the command.
  • <TRANSFER_CONFIG> (required): Resource to update; the reference defines `RESOURCE` as the resource to update.
  • --filter: Filters listed resources to match the supplied expression; the Dataplex metadata expression is specified by the release note.
  • --transfer_location (required): Location of transfer configurations to list.
  • --project_id (required): Project whose transfer configurations are listed.
  • Prerequisite: Run `bq` in Cloud Shell or install and configure the Google Cloud CLI for local use.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card