dev1
or use patterns such as dev*
to match any branch starting with dev,
or dev[12]
to match dev1
or dev2
.
A wildcard pattern *
can be used as a default option to catch all unmatched branches.
Branch name matching rules are evaluated sequentially, ensuring precise control
over the settings applied to each branch.
*
- matches all branchesprod
- matches prod
branchdev*
- matches all branches starting with dev
dev_[12]
- matches dev_1
and dev_2
dev_[!12]
- matches dev_3
, but not dev_1
and dev_2
prod
branch, defining a different ROLEsales
, defining a different WAREHOUSEsales
domain from the prod
branch, Honeydew will use the ROLE from the prod
environment configuration and the WAREHOUSE from the sales
domain configuration.
The following table shows the different options for defining Snowflake connection settings and their order of evaluation:
Setting | Global | Environment | Domain |
---|---|---|---|
Database | - | ✅ | - |
Schema | - | ✅ | - |
Warehouse | ✅ | ✅ | ✅ |
Role | ✅ | ✅ | ✅ |
prod
branch with a larger warehouse to handle higher workloads,
while the dev branch can use a smaller, cost-efficient warehouse.
When switching branches in Honeydew, the warehouse settings will automatically adjust based on predefined branch name rules, ensuring the right resources are used for each environment.
prod
branch.
The schema for environments is, for example: