Use the policy pushdown resync API to resynchronize all data access policies associated with an asset connection that you specify on your source system. Use this API when data access policies that you push down don't return expected results.
To run this API, you need the Governance Administrator role in Metadata Command Center role.
The policy pushdown resync API works with Databricks and Microsoft Fabric Data Lakehouse.
How this API ensures secure resynchronization
The policy pushdown resync API stops processing or pushing down data access policies to your source system. This API is useful when data access policies enter an undefined state and Data Governance and Catalog continually attempts to enforce the policies.
The policy pushdown resync API keeps your data safe while it resynchronizes data access control policies. It revokes permissions from the groups and reapplies them when the resynchronization is complete.
The policy pushdown resync API resynchronizes data filter policies without exposing data.
The API works in the following ways for each source system:
•For Databricks, the policy pushdown resync API replaces the row filter function. If the row filter function is already applied to the data, then it is still applied when Data Governance and Catalog replaces the function. There is no point when the table is without a row filter function.
•For Microsoft Fabric Data Lakehouse, the policy pushdown resync API 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 and then creates the data filter policy. Data Governance and Catalog handles concurrent creation conflicts by updating the existing filter predicate of the data filter policy.