Advanced Configuration for Collibra Tag Sync¶
The mandatory connection and routing properties are covered in Setup. The options below are optional and ship with safe defaults. In Privacera Manager, set the CONNECTOR_* variables in your vars.connector.collibra.yml file; each page also shows the rendered PolicySync property name.
| Configuration | Description |
|---|---|
| Tag Sync Schedule | Configure how often tag sync runs and whether it runs immediately at connector startup |
| Scan-Failure Safeguards | Protect against partial or failed Collibra scans deleting valid tag mappings (suspicious-delete threshold, circuit breaker, and built-in guards) |
| Collibra API Retry | Configure retry attempts and backoff for transient Collibra API failures |
| Connection Asset Type | Set the Collibra asset type used to locate connection assets |
| Tag Removal Behavior | How tag and tag-definition removals are applied to Ranger when tags are removed in Collibra |
| Sync to OMNI Metadata Service | Also create tags and tag-resource mappings in OMNI Metadata Service (MDS) when OMNI is enabled |
- Prev topic: Setup