Database

Usage

Database name = folder name of database
Config file in "database.yml" within database name folder

Snowflake Attributes

Parameter	Description
`DATA_RETENTION_TIME_IN_DAYS`	(Int) - Optional
`COMMENT`	(String) - Optional
`OWNER`	(String) - Optional If HANDLE_OWNERSHIP=ERROR, be careful not to set OWNER to a role that the deployer does not have access to as it will no longer have access to manage
`TAGS`	({KEY:VALUE}) - Optional
`GRANTS`	({KEY:VALUE}) - Optional

Optional Parameter Defaults - if omitted, Snowflake defaults for parameters are used, just like creating an object manually.

Deployment attributes

Parameter	Description
`DEPLOY_ENV`	(List) - Optional Default = [] List of the deployment environments to deploy to Deployment environment set in the environment config yaml using the DEPLOY_ENV parameter. See Setup/Config for docs. When empty or not included, deployed to all environments
`DEPLOY_LOCK`	(Bool) - Optional Default = False Locks the config file to being over written by reverse engineer process. Use if source code should always be source of truth and any changes pulled from database should be ignored

Folder Structure

snowflake/data/[database name]/database.yml

Example Structure

snowflake/data/MY_DATABASE1/database.yml

snowflake/data/MY_DATABASE2/database.yml

This creates 2 databases named "MY_DATABASE1" and "MY_DATABASE2" each with their own database.yml file within their respected folder

Samples

Basic

COMMENT: This is the comment on a database
OWNER: INSTANCEADMIN
DATA_RETENTION_TIME_IN_DAYS: 1
TAGS:
- {{ref('CONTROL__TAGS__ENV')}}: PROD
- {{ref('CONTROL__TAGS__ZONE')}}: ANALYTICS
GRANTS:
- {{role('SOME_ROLE')}}: USAGE

With a deploy lock & restricted deployment environments.

COMMENT: {{var_from_env_config}}
OWNER: INSTANCEADMIN
DATA_RETENTION_TIME_IN_DAYS: 1
TAGS:
- name: {{ref('CONTROL__GOVERNANCE__ENV')}}
  value: PROD
- name: {{ref('CONTROL__GOVERNANCE__ZONE')}}
  value: ANALYTICS
GRANTS:
- {{role('SOME_ROLE')}}: USAGE
DEPLOY_LOCK: true
DEPLOY_ENV:
- PROD
- TEST