-
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
Store when default env vars are used in manifest #5589
Conversation
…t-559-default-env-vars
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
eeb3325
to
9b20dd6
Compare
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.
Looks good, though I did have a couple of minor questions...
core/dbt/logger.py
Outdated
@@ -32,6 +32,7 @@ | |||
) | |||
|
|||
SECRET_ENV_PREFIX = "DBT_ENV_SECRET_" | |||
DEFAULT_ENV_PLACEHOLDER = "DBT_DEFAULT_PLACEHOLDER" |
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.
When it was just the SECRET_ENV_PREFIX, it felt kind of okay to have it in the logger file. But I'm not sure it does now. Can you think of a better place to put them? Particularly since eventually we do intend to get rid of logger.py...
* WIP * handle defauly env vars * fix typo * add changelog * small fixes * add constants.py file
* WIP * handle defauly env vars * fix typo * add changelog * small fixes * add constants.py file
resolves #5155
Description
Checklist
changie new
to create a changelog entry