add dbt_valid_to_current

[mirnawong1]

adding new config for dbt_valid_to_current, which allows users to set a future date for dbt_valid_to using the dbt_valid_to_current config in yaml/config/project.

Resolves #6275

Outstanding questions:
✅ - Can date be hardcoded using this syntax? "to_date('2024-05-10')" or can they use "to_date('2024, 05, 10')" ?
✅ - is the syntax just a string (e.g. dbt_valid_to_current: '9999, 12, 31' ) or must they use to_date?
✅ - can user use var to return a SQL statement '{{ var('my_future_date') }}'
✅ - can they use a macro that returns a SQL statement '{{ dbt.date(9999, 12, 31) }}'?
✅ - how does this new config work with deferral/state:modified? will we warn users that the config has been updated and they need to manually update their snapshot?

---

🚀 Deployment available! Here are the direct links to the updated files:

• https://docs-getdbt-com-git-add-custom-date-dbt-labs.vercel.app/docs/build/snapshots
• https://docs-getdbt-com-git-add-custom-date-dbt-labs.vercel.app/docs/dbt-versions/release-notes
• https://docs-getdbt-com-git-add-custom-date-dbt-labs.vercel.app/reference/resource-configs/dbt_valid_to_current

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs-getdbt-com	✅ Ready (Inspect)	Visit Preview	Nov 19, 2024 8:01pm

[dbeatty10]

@mirnawong1 grouping your outstanding questions into a handful of categories:

Hardcoded SQL expressions

Question:

• Can date be hardcoded using this syntax? "to_date('2024-05-10')" or can they use "to_date('2024, 05, 10')" ?

👍 Hardcoded expressions that work within the data platform is the only option that is available currently. The precise syntax will vary per warehouse, so to_date('2024-05-10') may work for some, but others may require something like date(2024, 5, 10).

Jinja within dbt_valid_to_current

Questions:

• is the syntax just a string (e.g. dbt_valid_to_current: '9999, 12, 31' ) or must they use to_date?
• can user use var to return a SQL statement '{{ var('my_future_date') }}'
• can they use a macro that returns a SQL statement '{{ dbt.date(9999, 12, 31) }}'?

👎 Jinja is not currently available for dbt_valid_to_current. So none of the above are possible, and the only option is to supply a full SQL expression that is specific to the users data warehouse.

Deferral / state:modified

Question:

• how does this new config work with deferral/state:modified? will we warn users that the config has been updated and they need to manually update their snapshot?

👍 Based on hands-on experimentation, it does work as expected with deferral / state:modified. So if this config changes, than it will show up when using --select state:modified.

[dbeatty10]

@mirnawong1 I added the blocked_by_dev label until this is resolved:

• [Bug] When a custom dbt_valid_to_current is configured, it doesn't update dbt-core#10921

[mirnawong1]

@mirnawong1 I added the blocked_by_dev label until this is resolved:

• [Bug] When a custom dbt_valid_to_current is configured, it doesn't update dbt-core#10921

thank you @dbeatty10 ! it looks like this is resolved now right?

[graciegoheen]

a few nits!

grace reviewed and folded in nits

[github-actions]

Check your created Crawler

Check your created index on your Algolia Application