feat (dbt): allow syncing only exposures #142
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This closes #141 |
anupreet
approved these changes
Nov 7, 2022
eschutho
reviewed
Nov 7, 2022
betodealmeida
force-pushed
the
sync-exposures-only
branch
from
a35c4e7
to
105500a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow syncing only exposures from Preset workspaces to a YAML file.
This now works with both dbt Cloud and dbt Core:
The datasets don't have to be created via the CLI for the exposure discovery to work. The command will look at all models (filtered by
--selectand--excluded, if set) and figure out which datasets correspond to them based on the the database, schema, and table name.