Repository navigation
feat: Write native destination plugin DDL to files with out executing them on destination #19258
Description
Which problem is this feature request solving?
I would like to write the DDL that will be executed to files, without executing them on the destination.
This will allow for:
- inspection before executing on the destination
- executing them manually or out-of-band on the desintation as-is
- allow for modifications before executing (like additional indexes, etc)
An example is given GCP source and Postgresql destination configs, write the SQL to create the tables files without creating/migrating the tables and without syncing.
Describe the solution you'd like
Perhaps adding "ddl" or "native" format to the --format flag.
cloudquery tables ./directory --filter spec --format native
The output is whatever code is generated to create the destination object (table, etc).
- postgresql would emit SQL
- etc
Pull request (optional)
- I can submit a pull request
Activity
erezrokah commentedon Oct 1, 2024
Hi @DougEverly, that's an interesting feature to have. Please note some plugins don't have a DDL per say, for example the S3 destination (or any file based destination). Others create the schema via Go APIs (like the BigQuery destination).
For the use case you outlines I belive the following:
Can be solved by the
cloudquery migratecommand, possible with thecloudquery sync --no-migratecommand and flag.For
Could be solved in a bit more involved way I think of running
cloudquery migratetowards a temporary/dedicate schema