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

Safe DAGs generation and deployment #288

Open
beczkowb opened this issue Sep 22, 2021 · 0 comments
Open

Safe DAGs generation and deployment #288

beczkowb opened this issue Sep 22, 2021 · 0 comments

Comments

@beczkowb
Copy link
Contributor

There are 2 problems when generating and deploying dags:

  1. Some workflows can be skipped when generating DAGs, due to errors on module import
  2. When we are deploying DAGs, we are not checking if there is an image with the proper version. There are 2 common reasons for DAGs and image mismatch – broken/forgotten image build and broken versioning.

First, we should throw an error when we can't import some module, and secondly, we should add a check in the DAGs deployment process, so it can throw an exception if there is no expected image. I'm not sure if we should make it as default (due to backward compatibility).

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

No branches or pull requests

1 participant