Skip to content

Resource Onboarding

This document provides information on how to use the resouce onboarding feature in BigQuery Connector.

In BigQuery connector, we have simplified the onboarding process for resources such as projects, datasets and tables in Privacera by replacing manual backend edits with an intuitive, user-friendly Admin UI. This interface will allow administrators to easily add, update, remove, and view resources, eliminating the need for technical tools and reducing errors.

Available Guides

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

    • One of the dataset from manage list is removed
    • Resource loader is updated.

    Resource Success Image

Limitations

  • This onboarding feature is only supported for managed resource properties (e.g., manage.project, manage.dataset, etc.). For other properties, users must first update in the portal, then download and copy the updated zip to the PM environment, and finally run PM setup followed by a helm upgrade.
  • Onboarding feature doesn’t support ignore resource list
  • The removing resource from managed list use-case has a limitation: If the tag-resource mapping is not cleared from the portal before removing a resource from the managed list, it will continue to persist in BigQuery UI.

  • To add/update properties that are not present on portal users need to use one of the following ways.

    1. Add property in connector YAML file directly.
    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.

    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