[Compatibility] Freshness is a `config` argument in dbt Fusion

[xrpza]

Is there an existing issue for this?

• I have searched the existing issues

Describe the issue

Description

In dbt versions <v1.9, freshness is a top-level argument. Going forward in dbt Fusion v.2.0 (beta) -- and already optional in dbt v1.9 -- freshness will be expected to be placed under the config arguments.

Failure to place freshness under config will result in deprecation warnings like the example below for users looking to leverage dbt Fusion v2.0 (beta).

// dbt Fusion warning during `dbtf build` operation

warning: (soon: error) dbt1060: Ignored unexpected key `"freshness"`. YAML path: `freshness`.
  --> dbt_packages/stripe_source/models/src_stripe.yml:698:9

// dbt v.10 warning during `dbt build` operation

18:26:51  [WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `stripe` in file
`models/src_stripe.yml`. The `freshness` top-level property should be moved into
the `config` of `stripe`.

Challenges

• The current stripe source dbt package supports dbt >= v1.3. Placing freshness under config instead of its current locus would likely break compatibility.

Wanted to open this issue to get the discussion going around this warning. Also happy to contribute where I can.

Relevant error log or model output

warning: (soon: error) dbt1060: Ignored unexpected key `"freshness"`. YAML path: `freshness`.
  --> dbt_packages/stripe_source/models/src_stripe.yml:698:9

Expected behavior

No deprecation warnings related to freshness are triggered as a result of using the stripe source package.

Possible solution

TBD, but options that immediately come to mind:

• Implementing a breaking change in the existing package that would require users to upgrade to at least dbt v1.9
• Forking the current package to spin-up a new "stripe source fusion" dbt package to support the mechanics of dbt >= v1.9 and dbt Fusion 2.0 (beta)

dbt Project configurations

Package versions

packages:
  - package: dbt-labs/codegen
    version: 0.13.1
    # https://hub.getdbt.com/dbt-labs/codegen/latest/
  - package: dbt-labs/dbt_utils
    version: 1.3.0
    # https://hub.getdbt.com/dbt-labs/dbt_utils/latest/
  - package: fivetran/ad_reporting
    version: [">=1.14.0", "<1.15.0"]
    # https://hub.getdbt.com/fivetran/ad_reporting/latest/
  - package: fivetran/stripe_source
    version:  [">=0.14.2", "<0.15.0"]
    # https://hub.getdbt.com/fivetran/stripe_source/latest/
  - package: godatadriven/dbt_date
    version: [">=0.13.0", "<0.14.0"]
    # https://github.com/godatadriven/dbt-date/tags

What database are you using dbt with?

snowflake

How are you running this dbt package?

dbt Cloud™

dbt Version

Core:
  - installed: 1.9.5
  - latest:    1.9.5 - Up to date!

Plugins:
  - snowflake: 1.9.4 - Up to date!

Additional Context

No response

Are you willing to open a PR to help address this issue?

• Yes.
• Yes, but I will need assistance.
• No.

[fivetran-jamie]

Hey @xrpza thanks for opening this and providing so much detail! We're currently investigating this and considering next steps. Will update ya here

[xrpza]

Thank you 🙏🏻 @fivetran-jamie

[fivetran-jamie]

Hey @xrpza thanks for your patience here!

We are going to update freshness to the new config framework and resolve this deprecation message. You can expect this to be live within the next 2 weeks or so.

For reference for anyone else looking, this means that to run freshness you will need to either:
A) Be on dbt core >= 1.9, or
B) Abstain from updating to the next release of this package and pin your dependency on the current version (stripe_source, or stripe if you're using that)

Otherwise, dbt source freshness will ignore the freshness tests in this package, as dbt Core < 1.9 will not recognize config.freshness

[fivetran-joemarkiewicz]

This update was addressed within PR #96 and the compatibility is now live in the latest version of the stripe packages.