GitHub
06/06/2026, 3:38 AMDue to our custom syntax for commands, using the executable name is going to be equally jarring when users get to executingI had a recent experience that I could see tripping people up. I wanted to use, which is not functionality of themeltano invoke great_expectations:checkpointexecutable.great_expectations
dbt docs generate and dbt docs serve which are not supported as dbt:x syntax because its not listed in the discovery.yml. This does not work:
meltano invoke dbt:docs generate
So I was thinking about adding an extra command to the plugin config like docs_generate that runs docs generate under the hood but then I realized that this works:
meltano invoke dbt docs generate
I'm not sure this is a problem but with such a minor difference in syntax I could see it becoming confusing whether your running a meltano command or raw command directly to the package. On one hand its great to allow commands to pass through so all the functionality is preserved but on the other its not clear in what context the command is being run. Maybe just having a warning that a "pass through" command is being used would be helpful, idk but wanted to call it out.
meltano/meltanoGitHub
06/06/2026, 3:38 AM