#7372 Running commands in `meltano run` creates difficult-to-understand output, vs `meltano invoke` of the same command Issue created by aaronsteers When run via

meltano invoke

, the output makes sense, is readable, and meets UX parity with invoking the plugin directly.

aj@ajs-macbook-pro jaffle-shop-template % meltano invoke dbt-duckdb:run

Extension executing

dbt clean

...

004431 Running with dbt=1.4.5

004431 Checking target/*

004431 Cleaned target/*

004431 Checking dbt_packages/*

004431 Cleaned dbt_packages/*

004431 Finished cleaning all paths.

Extension executing

dbt deps

...

004434 Running with dbt=1.4.5

004434 Installing dbt-labs/metrics

004435 Installed from version 1.4.0

004435 Updated version available: 1.4.1

004435 Installing dbt-labs/dbt_utils

004435 Installed from version 1.0.0

004435 Up to date!

004435

004435 Updates available for packages: ['dbt-labs/metrics']

Update your versions in packages.yml, then run dbt deps

Extension executing

dbt run

...

004437 Running with dbt=1.4.5

004437 Unable to do partial parsing because saved manifest not found. Starting full parse.

004439 Found 9 models, 20 tests, 0 snapshots, 0 analyses, 523 macros, 0 operations, 0 seed files, 6 sources, 0 exposures, 4 metrics

004439

004439 Concurrency: 4 threads (target='dev')

004439

004439 1 of 9 START sql view model analytics.stg_customers ............................ [RUN]

004439 2 of 9 START sql view model analytics.stg_locations ............................ [RUN]

004439 3 of 9 START sql view model analytics.stg_order_items .......................... [RUN]

004439 4 of 9 START sql view model analytics.stg_orders ............................... [RUN]

004439 2 of 9 OK created sql view model analytics.stg_locations ....................... [OK in 0.19s]

004440 4 of 9 OK created sql view model analytics.stg_orders .......................... [OK in 0.19s]

004440 1 of 9 OK created sql view model analytics.stg_customers ....................... [OK in 0.20s]

004440 3 of 9 OK created sql view model analytics.stg_order_items ..................... [OK in 0.55s]

004440 5 of 9 START sql view model analytics.stg_products ............................. [RUN]

004440 6 of 9 START sql view model analytics.stg_supplies ............................. [RUN]

004440 7 of 9 START sql table model analytics.dbt_metrics_default_calendar ............ [RUN]

004440 5 of 9 OK created sql view model analytics.stg_products ........................ [OK in 0.13s]

004440 6 of 9 OK created sql view model analytics.stg_supplies ........................ [OK in 0.13s]

004440 8 of 9 START sql incremental model analytics.orders ............................ [RUN]

004440 7 of 9 OK created sql table model analytics.dbt_metrics_default_calendar ....... [OK in 0.34s]

004441 8 of 9 OK created sql incremental model analytics.orders ....................... [OK in 0.87s]

004441 9 of 9 START sql table model analytics.customers ............................... [RUN]

004441 9 of 9 OK created sql table model analytics.customers .......................... [OK in 0.42s]

004441

004441 Finished running 6 view models, 2 table models, 1 incremental model in 0 hours 0 minutes and 2.10 seconds (2.10s).

004441

004441 Completed successfully

004441

004441 Done. PASS=9 WARN=0 ERROR=0 SKIP=0 TOTAL=9

The same command executed via

meltano run dbt:run

has significantly worse UX when compared with running

meltano invoke dbt:run

or

dbt run

directly:

aj@ajs-macbook-pro jaffle-shop-template % meltano run dbt-duckdb:run

2023-03-13T004928.364432Z [info ] Extension executing

dbt clean

... cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.305342Z [info ] 004930 Running with dbt=1.4.5 cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.325761Z [info ] 004930 Checking target/* cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.330316Z [info ] 004930 Cleaned target/* cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.330659Z [info ] 004930 Checking dbt_packages/* cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.377406Z [info ] 004930 Cleaned dbt_packages/* cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.377652Z [info ] 004930 Finished cleaning all paths. cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.930340Z [info ] cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.930580Z [info ] cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004930.931211Z [info ] Extension executing

dbt deps

... cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004932.912037Z [info ] 004932 Running with dbt=1.4.5 cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004933.384192Z [info ] 004933 Installing dbt-labs/metrics cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004933.669470Z [info ] 004933 Installed from version 1.4.0 cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004933.670279Z [info ] 004933 Updated version available: 1.4.1

cmd_type=command name=dbt-duckdb stdio=stderr

2023-03-13T004933.671266Z [info ] 004933 Installing dbt-labs/dbt_utils cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004933.921397Z [info ] 004933 Installed from version 1.0.0 cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004933.921810Z [info ] 004933 Up to date! cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004933.922547Z [info ] 004933 cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004933.922948Z [info ] 004933 Updates available for packages:

['dbt-labs/metrics'] cmd_type=command name=dbt-duckdb stdio=stderr

2023-03-13T004933.923182Z [info ] Update your versions in packages.yml, then run dbt deps

cmd_type=command name=dbt-duckdb stdio=stderr

2023-03-13T004934.459262Z [info ] cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004934.459560Z [info ] cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004934.460138Z [info ] Extension executing

dbt run

... cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004936.534167Z [info ] 004936 Running with dbt=1.4.5 cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004936.582745Z [info ] 004936 Unable to do partial parsing because saved

manifest not found. Starting full parse. cmd_type=command name=dbt-duckdb stdio=stderr

2023-03-13T004938.194708Z [info ] 004938 Found 9 models, 20 tests, 0 snapshots, 0

analyses, 523 macros, 0 operations, 0 seed files, 6 sources, 0 exposures, 4 metrics

cmd_type=command name=dbt-duckdb stdio=stderr

2023-03-13T004938.197610Z [info ] 004938 cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004938.293724Z [info ] 004938 Concurrency: 4 threads (target='dev')

cmd_type=command name=dbt-duckdb stdio=stderr

2023-03-13T004938.294151Z [info ] 004938 cmd_type=command

name=dbt-duckdb stdio=stderr

2023-03-13T004938.299789Z [info ] 004938 1 of 9 START sql view model

analytics.stg_customers ............................ [RUN] cmd_type=command name=dbt-duckdb

stdio=stderr

2023-03-13T004938.300392Z [info ] …

meltano/meltano