Skip to content

[DCV-3598] Document required Schema field for @task.datacoves_dbt service connections - #62

Open
fmercadop wants to merge 2 commits into
mainfrom
docs_fix_DCV-3598
Open

[DCV-3598] Document required Schema field for @task.datacoves_dbt service connections#62
fmercadop wants to merge 2 commits into
mainfrom
docs_fix_DCV-3598

Conversation

@fmercadop

Copy link
Copy Markdown
Contributor

Adds a warning to the @task.datacoves_dbt decorator docs and an explicit note on the service connections page stating that the Schema field is required when a service connection is used with @task.datacoves_dbt. Leaving it empty causes a dbt profile validation error at runtime (Credentials in profile "...", target "..." invalid: None is not of type 'string'), and it's easy to miss since the Airflow Snowflake provider docs list schema as optional for the Airflow connection itself.

…tions

Users leaving Schema empty on a Datacoves service connection hit a dbt
profile validation error ("None is not of type 'string'") that names
their own dbt profile, leading them to wrongly suspect the repo's
profiles.yml is being used instead of the generated temporary profile.
Clarify that Schema is required for @task.datacoves_dbt, and that the
Airflow Snowflake provider's "optional" schema applies to the Airflow
connection only, not the generated dbt profile.
@fmercadop
fmercadop requested a review from noel August 26, 2026 14:08
@fmercadop fmercadop self-assigned this Aug 26, 2026
Makes the existing defaults (connection details, profile name, target
name) and their overrides explicit and scannable instead of prose, per
request to clarify what @task.datacoves_dbt does out of the box vs.
what can be customized.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant