-
Notifications
You must be signed in to change notification settings - Fork 14
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
Feature request: For automation, add more defaults (and ideally, an all
option for some) for generate sources
#310
Comments
generate sources
all
option for some) for generate sources
all
option for some) for generate sources
all
option for some) for generate sources
@jaredx435k2d0 we've just added a new This allows you to automate the creation of resources, alongside the usage of already existent flags/args. For example, the following would generate all sources in all schemas on your DB:
It will auto-flatten and generate all the resulting resources with the filter(s) you use. A more complex filtering:
|
This is awesome! I'm planning to use some dbt-coves commands in a regular automation, so this will be perfect. Just to be clear, there is currently no way to choose to have it NOT flatten JSON, is that correct? |
Can you please explain the new |
Is your feature request related to a problem? Please describe.
I'm trying to run
generate sources
automatically via cron on a virtual machine. But, from what I can tell, there isn't a way to suppress some of the prompts (choose relations, flatten JSON, etc.).It also seems that I have to hardcode the schemas I'd like, using config.yml.
Describe the solution you'd like
I'd like a simple way to be able to generate sources for all relations in a schema, and for all schemas in a database.
I'd like to be able to have the following in my config
Describe alternatives you've considered
Not being able to automate it. Closest I've come is by hard coding my schemas in config.yml and then still needing to execute manually so I can interact with the prompts.
The text was updated successfully, but these errors were encountered: