Use CircleCI contexts for environment variables #754
Merged
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 N/A
This is a:
All pull requests from community contributors should target the
main
branch (default).Description & motivation
CircleCI has a capability of creating a named collection of environment variables called "contexts".
We've created one CircleCI Context per hosted data platform used in our integration tests:
CircleCI contexts included in a CI workflow take priority over project-level environment variables (according to this order of precedence). So if
ENV_VAR_123
is defined both at the project level and within a context, the project-specific one is not utilized.Checklist
star()
source)limit_zero()
macro in place of the literal string:limit 0
dbt.type_*
macros instead of explicit datatypes (e.g.dbt.type_timestamp()
instead ofTIMESTAMP