Greg Bernard
07/19/2023, 5:21 PMtest
method implemented which is required by the built-in test Op
dagster._core.errors.DagsterExecutionStepExecutionError: Error occurred while executing op "dbt_test_op":
The above exception was caused by the following exception:
AttributeError: 'DbtCli' object has no attribute 'test'
Using the built-in full_refresh
run config also tries to apply the flag to the CLI as --full_refresh
instead of --full-refresh
which returns an error when trying to run models.Greg Bernard
07/19/2023, 5:23 PMDbtCliResource
was deprecated in favour of DbtCli
, However in the base the former seems to already be removed?Greg Bernard
07/19/2023, 5:24 PMGreg Bernard
07/19/2023, 5:25 PMops:
run_dbt_0b7e2:
config:
full_refresh: true
Greg Bernard
07/19/2023, 5:30 PM"""Keyword arguments to pass to the underlying dbt command. Additional arguments not listed in the schema will
be passed through as well, e.g. {'bool_flag': True, 'string_flag': 'hi'} will result in the flags
'--bool_flag --string_flag hi' being passed to the dbt command.
"""
Greg Bernard
07/19/2023, 5:32 PMUsage: dbt build [OPTIONS]
Try 'dbt build -h' for help.
Error: No such option: --full_refresh Did you mean --full-refresh?
claire
07/19/2023, 6:17 PMGreg Bernard
07/20/2023, 1:51 PMfull-refresh: true
to the run config, but this is not the documented way it should work.rex
07/20/2023, 2:27 PMDbtCliResource
(formerly known as DbtCli
) to work with the existing out of the box ops.
In general, if you want to use the resource, we recommend that you just create your own `@op`’s that invoke DbtCliResource
since it gives you more control. There was an issue with this in the current release, but it was fixed this week with our 1.4.0 release.Greg Bernard
07/20/2023, 4:41 PM