Skip to content

Resource Onboarding in BigQuery Connector

This document explains how to use the resource onboarding feature in the BigQuery Connector.

The BigQuery Connector now streamlines the onboarding process for resources like projects, datasets, and tables in Privacera by replacing manual backend edits with a user-friendly Admin UI.

Use Cases

Update Managed Resource

  1. Update Managed Resource List by Adding New Resource

    • Current managed dataset list.

    Dataset list

    • Create Access Policy on the Managed Resource and add one resource that is not managed.

    Add Resource

    • The policy will be applied only for managed resources.
    • Update the managed resource list with the resource added in the created policy.

    Update Manage Resource List

    • The policy is now applied for the newly added resource.
    • Result: test_user1 is able to query tables from both datasets (test_dataset1, test_dataset2).

Remove Managed Resource

  • Remove any resource from manage resource list

    • Remove one of the dataset from manage list
    • Resource loader is updated.

    Resource Success Image

⚠ Limitations

  1. This onboarding feature supports only managed resource properties (i.e. manage.project, manage.dataset, manage.table). For other properties, you can:
    1. Update the property in the portal.
    2. Then download and copy the updated ZIP file to the jump server environment.
    3. Run the Privacera Manager setup and perform a Helm upgrade.
  2. The onboarding feature does not support the ignore resource list i.e. ignore.project, ignore.dataset, ignore.table.
  3. If the tag-resource mapping is not cleared from the portal before removing a resource from the managed list, it will persist in the BigQuery UI.
  4. To add or update properties that are not available in the portal, use one of the following methods:
    1. Method 1: Add a PM(Privacera Manager) variable for property in connector YAML file directly.

    2. Method 2: Custom directory

      • Create directory with name as custom inside your connector instance directory.
      • Add a file in that director named as connector-custom-properties.
      Bash
      1
2
3
      cd ~/privacera/privacera-manager
mkdir config/custom-vars/connectors/{Connector_Env_Name}/custom/ 
vi ~/privacera/privacera-manager/config/custom-vars/connectors/{Connector_Env_Name}/custom/connector-custom.properties

Comments