Use SchemaParser render context to render test configs #3646
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leahwicz
approved these changes
Jul 29, 2021
gshank
approved these changes
Jul 29, 2021
5 tasks
kwigley
pushed a commit
that referenced
this pull request
Jul 29, 2021
* use available context when rendering test configs * add test * update changelog
kwigley
pushed a commit
that referenced
this pull request
Jul 29, 2021
Closed
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resolves #3564
Description
Instead of creating a new context for the test builder to jinja render test configs, we can just use the context from the schema parser that has the right context properties to support
var()with project configured vars in addition to cli vars.Checklist
CHANGELOG.mdand added information about my change to the "dbt next" section.