feat: Manage local and remote Airflow variables during deployment #392
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
For more convenient collaboration, we need a consistent set of variables to be shared across developers working on the same datasets or pipelines. To do this, we're introducing a feature to compare locally set Airflow variables with those defined in Cloud Composer (remote).
Cases that are covered include
I've also added an optimization in the tests: skip formatting the code (takes a few seconds for every test case) for the setup step in
test_deploy_dag.py
.Checklist
Note: If an item applies to you, all of its sub-items must be fulfilled
README
accordingly