-
Notifications
You must be signed in to change notification settings - Fork 920
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add sl env var support #6106
base: current
Are you sure you want to change the base?
add sl env var support #6106
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -0,0 +1 @@ | |||
Use [Extended Attributes](/docs/dbt-cloud-environments#extended-attributes) and [Environment Variables](/docs/build/environment-variables) when connecting to the Semantic Layer. If you set a value directly in the Semantic Layer Credentials, it will have a higher priority than Extended Attributes. When using environment variables, the default value for the environment will be used. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aiguofer just double checking that the user would be adding this in their env settings and then adding DBT_ENV_SECRET
in the SL credentials page?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct.
For example, using something like {{env_var('DBT_WAREHOUSE')}}
to set the warehouse
value in your SL credentials would work.
Similarly, if you set your account
value in your connection using Extended Attributes with a value like {{env_var('DBT_ACCOUNT')}}
, we will now be able to do that look up for the Extended Attributes AND the env var.
you can now use ea or en vars to connect to SL.
this pr creates a snippet to add this info in various places.
linear and slack thread