You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you run a sync command, you can specify a target parameter. In dbt, this would set the schema for the models as they are defined in the profiles.yml file.
However, with the preset-cli, this parameter merely sets the database label used in Preset. The actual connection is based on the manifest.json file, which could have been compiled with a different target.
Desired Behavior
The target parameter should set the schema in the Preset connection to match the one defined in the profiles.yml file in dbt. This could be accomplished by either reading the YML file or recompiling dbt with the given target.
The text was updated successfully, but these errors were encountered:
Facing this issue right now.
I can't use the manifests produced by the prod pipeline since they were compiled with a different target than the one I use for preset. This is a long-standing issue, any hope for a fix?
When you run a sync command, you can specify a
target
parameter. In dbt, this would set the schema for the models as they are defined in theprofiles.yml
file.However, with the preset-cli, this parameter merely sets the database label used in Preset. The actual connection is based on the
manifest.json
file, which could have been compiled with a different target.Desired Behavior
The
target
parameter should set the schema in the Preset connection to match the one defined in theprofiles.yml
file in dbt. This could be accomplished by either reading the YML file or recompiling dbt with the given target.The text was updated successfully, but these errors were encountered: