collibra_tools
Use the collibra_tools group to read Collibra assets and related catalog
metadata. It is read-only: it never creates or changes Collibra records. Enable
the tool group for the agent and configure a named Collibra connection the
requesting user and agent may use. See Collibra integration
and Collibra connections.
collibra_tool
Ingestion fields inside
params:
Named list and search actions return the original REST response, including
results and paging information. Use the returned paging values to request
subsequent pages explicitly. GET_ASSET reads one asset by UUID. TEST_CONNECTION
authenticates and reports the number of assets visible to the connection; zero
visible assets is a failed visibility check.
For ingestion, FIND_TABLE accepts params.table_name and optionally a domain,
domain_id, or source_system; it returns matching candidates and marks ambiguous
results as requiring selection. Pass the chosen candidate’s UUID as asset_id to
GET_TABLE_METADATA. DISCOVER_TABLES requires a named domain, domain_id, or
source_system and returns candidate summaries. Lookup and discovery refuse scopes
over 2,000 typed tables. BULK_TABLES requires exactly one of table_names or
table_ids, with 1–500 entries. Names return candidate lookups; explicit UUIDs return
full metadata. Check pipeline_ready and blocked_reasons before building a pipeline;
unconfirmed approval, column order, missing metadata, or an unconfirmed table path is
a blocker. Configure nonstandard Collibra selectors through the connection’s optional
ingestion_model field; see Collibra ingestion.
REQUEST is
restricted to GET paths under /rest/2.0/ and does not accept a URL, body, or
authorization header. Ingestion reads pages sequentially (up to 100 pages of 500
per collection), then may make hierarchy requests and asset/attribute reads per
column; it can require many REST calls and makes no writes. See Collibra
integration for the read-only
boundary and access model.
