Policy pushdown resync API

The policy pushdown resync API resynchronizes the connection between Data Governance and Catalog and your source system. This pushes down all the data access policies again into your source system.

You must have the Governance Administrator Metadata Command Center role to run this API.

For Databricks, Data Governance and Catalog replaces the existing row filter function. If the row filter function is already applied to the table, then it will still be applied when the function is replaced. There is no point when the table is without a row filter function.

For Microsoft Fabric Data Lakehouse, Data Governance and Catalog creates a new security function and attaches it as a filter predicate on the target table. If the correct data filter policy already exists, Data Governance and Catalog atomically updates the predicate in place. If a different data filter policy is attached, Data Governance and Catalog detaches the old one first and then creates the data filter policy. Concurrent creation conflicts are handled gracefully by falling back to an alter if the data filter policy already exists.

The following table describes methods and endpoints for the data access policy resync API:

The base API URL differs for each pod. For more information, see Send requests.

To find the connection ID based on the name, you can use /api/v2/connection/name/<name>.

For more information, see Connections in the Administrator help.