0.27.0 - May 2024
This update introduces significant changes to SnowDDL permission model.
Potentially breaking changes
OWNERSHIP
onALERT
,DYNAMIC_TABLE
,EVENT_TABLE
,STAGE
are now granted to corresponding schema owner role. PreviouslyOWNERSHIP
for these objects types was assigned to SnowDDL admin role.New parameters were added for
SCHEMA
object type to support additional types of grants.
Config migration guide
For schemas with
ALERT
andDYNAMIC_TABLE
objects, use new parameterowner_warehouse_usage
to specify warehouses which can be used by schema owner role.For schemas with
ALERT
andSTAGE
object types, use existing parameterowner_integration_usage
to specify names of global integrations which can be used by schema owner role.For schemas with
ALERT
object type, add value- EXECUTE ALERT
to new parameterowner_account_grants
to allow execution of alerts in schema.For schemas with
TASK
object type, add value- EXECUTE TASK
to new parameterowner_account_grants
to allow execution of task in schema.For schemas with
ALERT
,DYNAMIC_TABLE
,PROCEDURE
accessing data in other schemas, make sure to use existing parameterowner_schema_read
to specify these schemas.
Code migration guide
If you use programmatic config, which creates
DatabaseBlueprint
orSchemaBlueprint
, make sure to add a new required parameterpermission_model
. This is how you can get default permission model, which is close to settings in previous SnowDDL versions:FutureGrant
object was changed. Now it accepts 4 parameters instead of 3 in the past. Parameteron
was renamed toon_future
, and new parameterin_parent
was added, which takesDATABASE
orSCHEMA
object type:
Any questions or problems?
You may create a new discussion on GitHub. Please provide as much context as possible. Sample configs and logs are very helpful as well.
Thank you!
Last updated