Skip to main content
Documentation
Feature Requests Onboarding Trust Center Status Page

Community

Transformations: Allow DBT Role to be configurable

Planned
Chip Ach User

We are running into an issue when running transforms using DBT (into Snowflake). The process works, but the resulting permissions structure isn’t quite right. We want the resulting tables/views to be owned by a Snowflake role called TRANSFORMER. Right now, the resulting tables/views are owned by the Snowflake user FIVETRAN_DBT_SERVICE which is what is used in the connector. This would be easily fixed by setting the ROLE variable in the profiles.yml that DBT uses to run, but it doesn’t look like we have the ability to edit that file (or set that via the UI).

Please sign in to leave a comment.

Comments

10 comments

Date Votes
  • Official comment
    Amy Peterson Fivetranner

    Hi Chip, 

    Thanks for this request! This is something we have heard from other customers, and we are working on the ability to define a separate warehouse user for dbt transformations. We expect this to be delivered in Q4 which ends January 31 for us. 

    Amy

  • Daniel Freilich User

    Hi Chip,

    Another solution to this was mentioned to me by the Fishtown team, and it involves using on-run-start hooks to change the role.

  • Alex LEATHARD User

    Hi Amy Peterson

    Any news on this feature?

    Thank you.

  • Amy Peterson Fivetranner

    Hi Alex, thanks for following up! This feature slipped to our Q1 which is Feb-April. We are working on it now and expect to have it rolled out to customers within the next couple weeks. 

  • Alex LEATHARD User

    Thanks for the update! I am fighting with this feature at the moment, so will be delighted when this is rolled-out. :)

  • Sandeep Kumar User

    Hi Amy,

    Any update on the feature? It would be great to have this feature.

  • Amy Peterson Fivetranner

    Hi Sandeep! This feature is currently in QA and we hope to start rolling it out to users in private preview in another week or two. I'll reach out to you and the others on this thread once it's available. Thanks!

  • Elliott User

    Any new updates related to this feature request? This is still a blocker for us to use dbt transformations with Fivetran.

  • Chris Riederer User

    FYI here is a workaround we are using.

    Let's say our original destination was called "snowflake_ingest". We made a separate destination called "snowflake_dbt". This destination goes to the same place (snowflake) but can have a different user and role. We now do all our transformations in snowflake_dbt and do no transformations in snowflake_ingest. All the connectors still live in snowflake_ingest.

    I hope this is helpful!

  • Sandeep Kumar User

    This is supported now, please ask FIvetran to enable it your account.