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

[Bug]: Consider pointing to the root of the dbt project in target-path using CLI option or env var #44

Open
edgarrmondragon opened this issue Nov 7, 2023 · 2 comments

Comments

@edgarrmondragon
Copy link
Contributor

edgarrmondragon commented Nov 7, 2023

Package Version

0.1.0

Python Version

NA

Operating System

NA

Description

Starting with dbt 1.7, the dbt clean command fails for directories outside of the project root: dbt-labs/dbt-core#8318.

Perhaps

target-path: ../.meltano/transformers/dbt/target
log-path: logs
packages-install-path: dbt_packages
clean-targets:
- ../.meltano/transformers/dbt/target
- dbt_packages
- logs
should be updated to point to a path in the transform/ directory.

Note

Setting target-path in dbt_project.yml is deprecated in favor of the CLI flag or env var: https://docs.getdbt.com/reference/project-configs/target-path#configuration

Code

No response

@edgarrmondragon edgarrmondragon changed the title [Bug]: Consider pointing to the root of the dbt project in target [Bug]: Consider pointing to the root of the dbt project in target-path using CLI option or env var Nov 7, 2023
@edgarrmondragon
Copy link
Contributor Author

Shared by a community member in Slack:

fwiw i got things to work by specifying DBT_CLEAN_PROJECT_FILES_ONLY: false in my env (via docker compose file), which lives here

@ilsaloving
Copy link

This issue has been stale for almost a year, and it really should be addressed. This issue blocks dbt from being used at all, unless the user jumps through hoops to discover the problem and then jury-rigs some mechanism for injecting DBT_CLEAN_PROJECT_FILES_ONLY into the run.

If there are no plans to fix the underlying paths issue, this flag should be enabled by default in the plugin.

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

2 participants