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
Custom run artifacts path #38
Conversation
Hey @Fszta, thanks for adding this! Would you happen to have a bit of time to resolve the conflict in Thanks! |
Hi @mrshu, done :) I've slightly updated the error message to make it more consistent with both case, custom or default folder |
Thanks a lot @Fszta, this looks nice! Would you mind adding yourself to the Thanks again! |
Sorry @Fszta, the merges from other PRs have made this such that there are again conflicts... Would you mind resolving them one last time please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a bunch @Fszta!
Thanks again @Fszta, this was now released in I also took the liberty of adding a bit of documentation on it in the README: https://github.com/slidoapp/dbt-coverage#custom-run-artifacts-path-with---run-artifacts-dir Hope you like it! |
Goal
Give more flexibility to user who have their manifest.json & catalog.json files not stored in /target, which is mainly the case for user using dbt cloud (need to retrieve the file by api call), adding a new parameter to use a custom path allow user not to create an unnecessary
target
dir in their cicd pipelineDescription
run_artifacts_dir : Path
parameter to load_manifest and load_catalogrun_artifacts_dir
parameter to cli