Transformations: Allow for DBT secret environment variables
With our data workflow, we leverage private dbt packages that contain business logic that is used across our ecosystem. However, since this information is proprietary, we don't have these repositories public and we set up access to them using Personal Access Tokens through GitHub. The issue is that we set up the personal access token to access those private packages as explained here: https://docs.getdbt.com/docs/build/packages#private-packages, but the personal access token is stored in plain text.
In order for transformations to build correctly in Fivetran, you must input this variable but there is no option to add secret variables and any variables specified in the transformation information is stored in plain text. A feature that I would like to see is including a section for dbt secret variables (prefixed with DBT_ENV_SECRET) to be stored within Fivetran. This also ensures that no sensitive variables are contained within logs shown in the Fivetran UI. Additionally, any secret variables are stored in Fivetran like passwords, where looking at the transformation information will not allow you to copy the secret.
Please sign in to leave a comment.
Comments
0 comments