Problem
With dbt 1.10's improved YAML validation, the current test configuration syntax in stg_ga4__event_page_view.yml triggers a deprecation warning. While this doesn't cause failures by default, it prevents teams from using the --warn-error flag for stricter validation during CI/CD.
Warning Output
❯ dbt parse --warn-error
Compilation Error
Invalid generic test configuration given in models/staging/events/stg_ga4__event_page_view.yml:
[WARNING][MissingArgumentsPropertyInGenericTestDeprecation]: Deprecated functionality
Found top-level arguments to test `not_null`. Arguments to generic tests should
be nested under the `arguments` property.
Root Cause
The test configuration uses the older inline syntax:
- not_null:
severity: warn
The updated format uses a config block (see dbt docs on severity):
- not_null:
config:
severity: warn
Note: The config block syntax is backward compatible and works with older dbt versions, so this change won't break compatibility for users not yet on dbt 1.10.
Impact
- Blocks use of
--warn-error flag for strict validation in CI/CD pipelines
- dbt 1.10's improved validation now detects and warns about this older syntax
- Future dbt versions may remove support for the deprecated syntax
Problem
With dbt 1.10's improved YAML validation, the current test configuration syntax in
stg_ga4__event_page_view.ymltriggers a deprecation warning. While this doesn't cause failures by default, it prevents teams from using the--warn-errorflag for stricter validation during CI/CD.Warning Output
Root Cause
The test configuration uses the older inline syntax:
The updated format uses a
configblock (see dbt docs on severity):Note: The
configblock syntax is backward compatible and works with older dbt versions, so this change won't break compatibility for users not yet on dbt 1.10.Impact
--warn-errorflag for strict validation in CI/CD pipelines