-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
check env variables for profile configs #450
Comments
I (and others) would love to see this. Our ops team wants us to avoid writing arbitrary flat files as a part of the deploy process, and we can't check in secrets to our repositories.
This seems little different than the
This would definitely work, but might get unwieldy depending on how many connections you have
This again could get hairy if you have multiple connections, but it's closest to what I have in mind. I could also imagine something where in a secrets-free |
This is really great feedback, thanks @enkeboll. Here's where my head goes: If we parse the my-profile:
outputs:
prod:
type: redshift
host: "{{ env('DBT_HOST') }}"
user: "{{ env('DBT_USER') }}"
pass: "{{ env('DBT_PASS') }}"
port: 5439
dbname: analytics
schema: analytics
threads: 1
target: prod Definitely open to alternatives here though. |
Love it! I think that's an ideal solution. |
This could work by:
profiles.yml
fileprofiles
infoThe text was updated successfully, but these errors were encountered: