Adding New ENV var to file #116
Merged
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
…mcknight/integration.yml
kwigley
approved these changes
Feb 11, 2022
|
Thank you @kwigley |
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.
Description
adding a new
BIGQUERY_TEST_NO_ACCESS_DATABASEenv variable to main as we use current main branch to test against pr's so tests involving the new env var are currently failingWill reference in changelog for primary PR as this is just a required pr to be able to properly test 111 and provide a simple integration test for community contribution.
Checklist
CHANGELOG.mdand added information about my change to the "dbt-bigquery next" section.