8000 Make the dbt target path (not just the target) customizable under the dbt templater settings · Issue #6405 · sqlfluff/sqlfluff · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Make the dbt target path (not just the target) customizable under the dbt templater settings #6405

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

Closed
3 tasks done
wircho opened this issue Oct 26, 2024 · 0 comments · Fixed by #6423
Closed
3 tasks done
Labels
enhancement New feature or request

Comments

@wircho
Copy link
Contributor
wircho commented Oct 26, 2024

Search before asking

  • I searched the issues and found no similar issues.

Description

The dbt target path is where dbt stores parsing/compilation artifacts. This defaults to target/ and is globally customizable via the project's dbt_project.yml's target-path element. It can also be specified on individual dbt commands via a --target-path <TARGET DIRECTORY NAME> argument.

It would be useful if this path were customizable for SQLfluff commands under the [sqlfluff:templater:dbt] configuration.

Use case

My team has a dbt repo used by many data engineers and data scientists. Artifacts from dbt commands are an important part of our workflow (we leverage them for partial parsing and project navigation), so ideally we want artifacts from sqlfluff commands to end up in a different target directory.

Dialect

Any

Are you willing to work on and submit a PR to address the issue?

  • Yes I am willing to submit a PR!

Code of Conduct

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

Successfully merging a pull request may close this issue.

1 participant
0