Custom Service Repo for Access Management for Starburst Trino¶

• Open the vars.trino.opensource.yml file and update the following configuration:

  Bash
  1 2	### This is for hive catalog TRINO_HIVE_POLICY_REPO_CATALOG_MAPPING: "custom_hive_repo_1:catalog_1;custom_repo_2:catalog_2,catalog_3"

  Bash
  1 2	### This is for catalog other than hive catalog TRINO_RANGER_SERVICE_REPO: "custom_trino_repo"

• After configuring the properties, start the connector by executing the following instructions: Step 1 - Setup which generates the helm charts. This step usually takes few minutes.

  Bash
  1 2	cd ~/privacera/privacera-manager ./privacera-manager.sh setup

  Step 2 - Apply the Privacera Manager helm charts.

  Bash
  1 2	cd ~/privacera/privacera-manager ./pm_with_helm.sh upgrade

  Step 3 - (Optional) Post-installation step which generates Plugin tar ball, updates Route 53 DNS and so on. This step is not required if you are updating only connector properties.

  Bash
  1 2	cd ~/privacera/privacera-manager ./privacera-manager.sh post-install

• Follow the steps to copy the configuration files and rebuild the image by Following these steps

  Note

  If the custom service repo is not defined, the plugin will use default service repos.

Add the keys under Custom Properties while configuring the connector.

The key must match its name in install.properties exactly. A name that is not already in that file is appended as a line nothing reads.

For a connector that is already deployed, save it, download the bundle again, and rebuild the image. The change reaches the plugin only through a freshly downloaded bundle.