You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v1.2 will include a schema change for manifest.json, with the addition of the grants: {} default config. We'll need to update, document v6, and add/declare backwards compatibility (per #5346):
As I've said many many times before (in #4617 as elsewhere):
I'm interested in any small, tactical lifts we can make so that we're not bumping the manifest schema version in every single new minor version. At the same time, we're eager to provide other interfaces into manifest information, over which we have more control
Given that config can accept any values, it probably makes more sense to treat this in our JSONSchema as a dict[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.
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: