-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CT-781] Bump manifest schema to v6 for v1.2 #5417
Comments
github-actions
bot
changed the title
Bump manifest schema to v6 for v1.2
[CT-781] Bump manifest schema to v6 for v1.2
Jun 28, 2022
AC:
|
Issue for updating docs: dbt-labs/docs.getdbt.com#1667 |
|
I think this one is resolved! We have a separate issue to track the docs update |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
v1.2 will include a schema change for
manifest.json
, with the addition of thegrants: {}
default config. We'll need to update, documentv6
, and add/declare backwards compatibility (per #5346):dbt-core/core/dbt/contracts/graph/manifest.py
Lines 1138 to 1140 in d5608dc
As I've said many many times before (in #4617 as elsewhere):
Given that
config
can accept any values, it probably makes more sense to treat this in our JSONSchema as adict[str, Any]
, rather than inferring its defaults from the node config classes.The ability to declare backwards compatibility does remove this as an issue for most end users, but it remains true that we're creating unneeded manual work for metadata consumers.
This will also require updates to:
The text was updated successfully, but these errors were encountered: