Skip to content
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

Merged
merged 7 commits into from
Aug 3, 2022

Conversation

emmyoop
Copy link
Member

@emmyoop emmyoop commented Aug 1, 2022

resolves #5155

Description

Checklist

@cla-bot cla-bot bot added the cla:yes label Aug 1, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Aug 1, 2022

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.

@emmyoop emmyoop changed the title Er/ct 559 default env vars Store when default env vars are using in manifest Aug 1, 2022
@emmyoop emmyoop changed the title Store when default env vars are using in manifest Store when default env vars are used in manifest Aug 1, 2022
@emmyoop emmyoop marked this pull request as ready for review August 2, 2022 16:55
@emmyoop emmyoop requested review from a team as code owners August 2, 2022 16:55
@emmyoop emmyoop requested review from nathaniel-may, lostmygithubaccount and gshank and removed request for a team, nathaniel-may and lostmygithubaccount August 2, 2022 16:55
Copy link
Contributor

@gshank gshank left a 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...

.changes/unreleased/Under the Hood-20220802-112936.yaml Outdated Show resolved Hide resolved
core/dbt/context/providers.py Outdated Show resolved Hide resolved
@@ -32,6 +32,7 @@
)

SECRET_ENV_PREFIX = "DBT_ENV_SECRET_"
DEFAULT_ENV_PLACEHOLDER = "DBT_DEFAULT_PLACEHOLDER"
Copy link
Contributor

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...

@emmyoop emmyoop requested review from a team and iknox-fa August 3, 2022 01:24
@emmyoop emmyoop merged commit 4f5b9e6 into main Aug 3, 2022
@emmyoop emmyoop deleted the er/ct-559-default-env-vars branch August 3, 2022 01:53
VersusFacit pushed a commit that referenced this pull request Sep 5, 2022
* WIP

* handle defauly env vars

* fix typo

* add changelog

* small fixes

* add constants.py file
agoblet pushed a commit to BigDataRepublic/dbt-core that referenced this pull request Sep 16, 2022
* WIP

* handle defauly env vars

* fix typo

* add changelog

* small fixes

* add constants.py file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CT-559] [Bug] Partial parser does not recognize default values in envvars
2 participants