Handling Duplicate Assets During Key Pair Authentication Switch in Snowflake Collibra Integration
Summary: Vipul Sharma highlights challenges faced by their organization during Snowflake's transition from service credentials to key pair authentication. They specifically mention issues with integrating Collibra, where launching metadata scans with the new authentication method sometimes results in duplicate assets. While handling duplicates is manageable, transferring existing asset curation to new assets under the new method is challenging. Vipul Sharma seeks advice or tools from others who might have solutions to facilitate bulk curation transfer in this context.
As Snowflake transitions from service credentials to key pair authentication, our organization is encountering issues during integration with Collibra. Specifically, when launching metadata scans using the new key pair authentication, duplicate assets can appear. While managing duplicates is relatively straightforward, transferring existing asset curation (like descriptions, tags, and business associations) from the old connection to the new one poses significant challenges. Has anyone implemented effective strategies or developed tools to facilitate bulk curation transfer to the newly created assets under the new authentication method? Sharing your experiences or solutions will greatly benefit community members facing similar challenges.
Brian Lloyd
·2 months agoI experience the same issue when our Tableau Online developers move reports from folder to folder (likely to clean up and organize the access better). Any manually enriched metadata is tied in the now "Missing from source" assets and the new assets are minimally completed as a fresh new asset. Is Collibra building any capabilities to address the regular migration activity, so we don't have to export to excel and futz with things then reimport??