Skip to content

Tag Definition Deletion

When a tag is removed from an asset in Collibra, the connector always removes the tag-resource mapping — the tag is unlinked from the table or column. Whether the leftover tag definition is also deleted (when no asset uses it anymore) is controlled by the property below. See Tag Removal Behavior for how the removal itself is applied, and Scan-Failure Safeguards for the guards that prevent an incomplete scan from triggering deletes.

Configurable property

PolicySync Property Privacera Manager Variable Description Default
tag.sync.skip.delete.tagdefs CONNECTOR_TAG_SYNC_SKIP_DELETE_TAGDEFS When true, tag definition deletions are skipped — only the tag-resource mapping is removed and the definition is kept. When false, an orphaned tag definition (no longer used by any asset) is also deleted so Ranger stays in sync with Collibra. Defaults to false for Collibra. false

Note

On the Ranger destination this is safe: Ranger refuses to delete a tag definition that is still mapped by another service or connector, so shared tags are never removed. When OMNI/MDS is the destination and you want tag definitions preserved in the metadata store, set this to true.

Configuration

  1. SSH to the instance where Privacera Manager is installed.

  2. Run the following command to open the .yml file to be edited.

    If you have multiple connectors, then replace instance1 with the appropriate connector instance name.

    Bash
    1
    vi ~/privacera/privacera-manager/config/custom-vars/connectors/collibra/instance1/vars.connector.collibra.yml

  3. Update or add the following property:

    YAML
    1
    CONNECTOR_TAG_SYNC_SKIP_DELETE_TAGDEFS: "false"

  4. Once the property is configured, run the following commands to update your Privacera Manager platform instance:

    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