Configure a Google BigQuery Integration

Private preview: This integration is available to select accounts. Reach out to your Immuta representative for details.

The Google BigQuery resource allows you to create, configure, and manage your Google BigQuery integration. In this integration, Immuta generates policy-enforced views in your configured Google BigQuery dataset for tables registered as Immuta data sources.

Use the /integrations endpoint to

Requirements

  • APPLICATION_ADMIN Immuta permission

  • Google BigQuery integration enabled in Immuta (work with your Immuta representative to enable this integration)

  • To execute the Immuta script from your command line to create a Google Cloud service account and role, you must be authenticated to the gcloud CLI utility as a user with all of the following roles:

    • roles/iam.roleAdmin

    • roles/iam.serviceAccountAdmin

    • roles/serviceusage.serviceUsageAdmin

Prerequisite

Create a Google Cloud service account and role by either using the Google Cloud console or the provided Immuta script.

Configure the integration

  1. Copy the request example. The example uses JSON format, but the request also accepts YAML.

  2. Replace the Immuta URL and API key with your own.

  3. Change the config values to your own, where

    • role is the Google Cloud role used to connect to Google BigQuery.

    • datasetSuffix is the suffix to postfix to the name of each dataset created to store secure views. This string must start with an underscore.

    • dataset is the name of the BigQuery dataset to provision inside of the project for Immuta metadata storage.

    • location is the dataset's location, which can be any valid GCP location (such as us-east1).

    • credential is the Google BigQuery service account JSON keyfile credential content. See the Google documentation for guidance on generating and downloading this keyfile.

See the config object description for parameter definitions, value types, and additional configuration options.

Response

The response returns the status of the Google BigQuery integration configuration connection. See the response schema reference for details about the response schema.

A successful response includes the validation tests statuses.

Get an integration

  1. Copy the request example.

  2. Replace the Immuta URL and API key with your own.

  3. Replace the {id} request parameter with the unique identifier of the integration you want to get. Alternatively, you can get a list of all integrations and their IDs with the GET /integrations endpoint.

Response

The response returns a Google BigQuery integration configuration. See the response schema reference for details about the response schema. An unsuccessful response returns the status code and an error message. See the HTTP status codes and error messages for a list of statuses, error messages, and troubleshooting guidance.

Get all integrations

  1. Copy the request example.

  2. Replace the Immuta URL and API key with your own.

Response

The response returns the configuration for all integrations. See the response schema reference for details about the response schema. An unsuccessful request returns the status code and an error message. See the HTTP status codes and error messages for a list of statuses, error messages, and troubleshooting guidance.

Update an integration configuration

  1. Copy the request example, which updates the private key. The example uses JSON format, but the request also accepts YAML.

  2. Replace the Immuta URL and API key with your own.

  3. Replace the {id} request parameter with the unique identifier of the integration you want to update.

  4. Change the config values to your own, where

    • role is the Google Cloud role used to connect to Google BigQuery.

    • datasetSuffix is the suffix to postfix to the name of each dataset created to store secure views. This string must start with an underscore.

    • dataset is the name of the BigQuery dataset to provision inside of the project for Immuta metadata storage.

    • location is the dataset's location, which can be any valid GCP location (such as us-east1).

    • credential is the Google BigQuery service account JSON keyfile credential content. See the Google documentation for guidance on generating and downloading this keyfile.

See the config object description for parameter definitions, value types, and additional configuration options.

Response

The response returns the status of the Google BigQuery integration configuration connection. See the response schema reference for details about the response schema.

A successful response includes the validation tests statuses.

Delete an integration

  1. Copy the request example.

  2. Replace the Immuta URL and API key with your own.

  3. Replace the {id} request parameter with the unique identifier of the integration you want to delete.

Response

The response returns the status of the Google BigQuery integration configuration that has been deleted. See the response schema reference for details about the response schema. An unsuccessful request returns the status code and an error message. See the HTTP status codes and error messages for a list of statuses, error messages, and troubleshooting guidance.

Last updated

Was this helpful?