Add copy_grants config for Snowflake

[thutuva]

Summary:
Tables and views that have been replicated for a Snowflake share will drop from the share when the table/view is refreshed in dbt. A copy_grants config needs to be added to prevent this from happening. If this config is added to the dbt_project.yml then all models, including in packages, will be given the correct permissions to they don't drop from the share.

Point to discuss with the team:
Should we add +copy_grants: true to the Tuva Project?

• Pro - tables/views will not get dropped if an open-source user needs to replicate their tables for a Snowflake share.
• Con - it's redundant because you will have to add this config to your dbt_project.yml for your other (non package) models

Current behavior:
Re-running a dbt project will refresh the data and update the drop tables and views that have been refreshed from a replicated Snowflake share.
Expected behavior:
Re-running a dbt project will refresh the data and update the tables and views that have been replicated for a Snowflake share.

[aneiderhiser]

I don't think we need to build this sort of functionality into the Tuva Project. This is Snowflake data eng functionality, not healthcare analytics. When we're implementing TTP on internal datasets or for customers we'll have a separate dbt project (that imports TTP) where we can add this functionality.

[thutuva]

I will close this out then.