Model property deprecation_date

[matthewshaver]

What are you changing in this pull request and why?

Adding new model property deprecation_date
Create new model property card
Add to existing table of properties

Checklist

Uncomment if you're publishing docs for a prerelease version of dbt (delete if not applicable):

• Add versioning components, as described in Versioning Docs
• [TODO] Add a note to the prerelease version Migration Guide
• Review the Content style guide and About versioning so my content adheres to these guidelines.
• Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding new pages (delete if not applicable):

• Add page to website/sidebars.js
• Provide a unique filename for the new page

Link to Core repo PR

dbt-labs/dbt-core#7562

[netlify]

✅ Deploy Preview for docs-getdbt-com ready!

Name	Link
🔨 Latest commit	ddb5b02
🔍 Latest deploy log	https://app.netlify.com/sites/docs-getdbt-com/deploys/64a594c5e4597f000832794a
😎 Deploy Preview	https://deploy-preview-3579--docs-getdbt-com.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[dbeatty10]

This is looking good!

I added inline suggestions for using a full "aware" datetime rather than just a "naive" date.

See below for two more suggestions.

1. Model governance

It seems like we should update https://docs.getdbt.com/docs/collaborate/govern/model-versions to add a section and examples for deprecation_date.

2. Supported formats

I haven't tried any of these formats yet, but I'd hope / expect that they all work:

canonical: 2001-12-15T02:59:43.1Z
iso8601: 2001-12-14t21:59:43.10-05:00
spaced: 2001-12-14 21:59:43.10 -5
date: 2002-12-14

In particular, I'm hoping that all RFC 3339 timestamp formats are supported (as well as the most common ISO 8601 formats).

See here for examples of different formats:
https://dbeatty10.github.io/rfc3339-iso8601/

[dbeatty10]

See datetime format comment above.

[jtcohen6]

Agree with Doug -- we should add a new section to the docs on "Model Versions" about deprecation_date, and also update anywhere where we've said "in the future":

In the future, dbt will also offer first-class support for deprecating models (dbt-core#7433).

dbt will notify consumers of your versioned model when new versions become available, or (in the future) when they are slated for deprecation

Because dbt knows that these models are actually the same model, it can notify downstream consumers as new versions become available, and (in the future) as older versions are slated for deprecation.

[mirnawong1]

trying to fix deploy preview build error

[mirnawong1]

fixed the deploy error and the preview looks fine. two questions, i wanted to flag is:

• do we want to version the model-properties code so deprecation_date appears if you're on 1.6 or higher? or are actively showing it so ppl can upgrade versions?
• should we add deprecation_date in the https://docs.getdbt.com/docs/collaborate/govern/model-versions page?