(Sorry if wrong channel) So, if I'm not mistaken

meltano elt

command is going to be deprecated in favor of `run`(?) Right now I find it very useful to be able to dump extractor/loader config with elt like:

MELTANO_ENVIRONMENT=prod meltano elt tap-mongodb--bra target-bigquery --dry --dump loader-config

How do I do the same thing when

elt

is replaced with

run

?

@andrey_tatarinov you could use invoke:

meltano invoke --dump config tap-readthedocs

Would that work for you?

Not really, as discussed in the previous thread in my case loader configuration depends on extractor through

load_schema

setting. And I would like to confirm that extractor/loader configuration is consistent and produces intended results in every environment. https://meltano.slack.com/archives/C01UTUSP34M/p1653844485900109

We do have

--dry-run

support in

meltano run

. Dumping config files for inspection might become a feature of

meltano run

or could be a future extension to

meltano config

. I know we've discussed this in various threads but I'm not sure if it has a dedicated issue yet. Also - Just as we still will support

meltano invoke

because it gives more precise/surgical control of CLI args when running just a single command, there might still be long term use cases for

meltano elt

(or

meltano el

or similar) when surgical/experimental one-off executions. We want to encourage all prod and dev/test use cases go through

meltano run

because it is simpler, safer execution pattern when actually running defined workloads.

We have https://gitlab.com/meltano/meltano/-/issues/3144

Thanks, will keep an eye on this issue!

For your use case, I think this could make sense as an extension of

meltano config

(as proposed here, but perhaps doesn't solve the tap/target pairing test) or else a feature addition to

meltano run

, something like

--dryrun --config-cleanup=false

.