0.45.0 - March 2025

This release introduced a few breaking changes related to custom resolver sequences. If you do not override standard SnowDDL classes and resolver sequences, nothing should change.

Changes

• Separated DatabaseAccessRoleResolver into:

  • DatabaseOwnerRoleResolver

  • DatabaseReadRoleResolver

  • DatabaseWriteRoleResolver

• Separated SchemaAccessRoleResolver into:

  • SchemaOwnerRoleResolver

  • SchemaReadRoleResolver

  • SchemaWriteRoleResolver

• Separated WarehouseAccessRoleResolver into:

  • WarehouseMonitorRoleResolver

  • WarehouseUsageRoleResolver

How to adapt resolver sequences?

Find:

    DatabaseAccessRoleResolver,
    SchemaAccessRoleResolver, 

Replace with:

    DatabaseReadRoleResolver,
    DatabaseWriteRoleResolver,
    SchemaReadRoleResolver,
    SchemaWriteRoleResolver,
    DatabaseOwnerRoleResolver,
    SchemaOwnerRoleResolver,

"Owner" roles should always be processed AFTER "read" and "write" roles.

---

Find:

    WarehouseAccessRoleResolver,

Replace with:

    WarehouseMonitorRoleResolver,
    WarehouseUsageRoleResolver,

This changes was made in order to unify code for objects with multiple role types.

Using owner_schema_* parameters for DATABASE object type

It is now possible to define owner_schema_read and owner_schema_write for DATABASE object type. Previously these parameters were not available due to resolver execution order.