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.

Sign up for GitHub

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

Jump to bottom

Add DbtDepsOperator to DbtDag and DbtTaskGroup #79

Closed
chrishronek opened this issue Jan 10, 2023 · 1 comment
Closed

Add DbtDepsOperator to DbtDag and DbtTaskGroup #79

chrishronek opened this issue Jan 10, 2023 · 1 comment
Assignees
@chrishronek
Labels
wontfix This will not be worked on

Comments

@chrishronek
Copy link
Contributor

chrishronek commented Jan 10, 2023 •
edited
Loading

The extract DAG for the mrr-playbook example was failing after initializing the cosmos-dev sandbox. This is because mrr-playbook has a packages.yml file with defined dependencies. After creating the DbtDepsOperator and discussing with @jlaneve, we decided that there should be a DbtDepsOperator generated at as the first task of any DbtDag or DbtTaskGroup class (if a packages.yml exists in that project).

We'll work on this after this is merged.
@chrishronek chrishronek added bug Something isn't working enhancement New feature or request labels Jan 10, 2023
@chrishronek chrishronek self-assigned this Jan 10, 2023
@chrishronek chrishronek added wontfix This will not be worked on and removed bug Something isn't working enhancement New feature or request labels Feb 1, 2023
@chrishronek
Copy link
Contributor Author

Customers can put this before the DbtTaskGroup parser to install deps as needed. Not worth adding to the parser at this time.

@chrishronek chrishronek closed this as not planned Won't fix, can't repro, duplicate, stale Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chrishronek chrishronek

Labels
wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chrishronek