chore(dbt sync): Deprecate using the dbt_project file to trigger a dbt sync #299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's possible to trigger the dbt Core sync specifying the path to either the
manifest.json
file or to thedbt_project.yml
file. The former would currently display aDeprecationWarning
.dbt deprecated the
target-path
as a config in thedbt_project.yml
(which is used when triggering the command with this file) so this PR is moving the deprecated warning to when syncing with the path todbt_project.yml
file specified. For simplicity, I would recommend dropping support entirely in a future release and relying solely in themanifest.json
file.This PR also moves away from using
warnings.warn()
as it breaks logging (not a concern when using thepreset-cli
as a standalone CLI, but could be impactful when using it as a dependency and relying on its methods).