Skip to content

Use dynamic schema names rather than hardcoded ones #102

Use dynamic schema names rather than hardcoded ones

Use dynamic schema names rather than hardcoded ones #102

Workflow file for this run

# **what?**
# Run tests for dbt-codegen against supported adapters
# **why?**
# To ensure that dbt-codegen works as expected with all supported adapters
# **when?**
# On every PR, and every push to main and when manually triggered
name: Package Integration Tests
on:
push:
branches:
- main
pull_request:
workflow_dispatch:
jobs:
run-tests:
uses: dbt-labs/dbt-package-testing/.github/workflows/run_tox.yml@v1
# this just tests with postgres so no variables need to be passed through.
# When it's time to add more adapters you will need to pass through inputs for
# the other adapters as shown in the below example for redshift
with:
# snowflake
SNOWFLAKE_USER: ${{ vars.SNOWFLAKE_USER }}
SNOWFLAKE_ROLE: ${{ vars.SNOWFLAKE_ROLE }}
SNOWFLAKE_DATABASE: ${{ vars.SNOWFLAKE_DATABASE }}
SNOWFLAKE_WAREHOUSE: ${{ vars.SNOWFLAKE_WAREHOUSE }}
SNOWFLAKE_SCHEMA: "integration_tests_snowflake_${{ github.run_number }}"
secrets:
SNOWFLAKE_ACCOUNT: ${{ secrets.SNOWFLAKE_ACCOUNT }}
DBT_ENV_SECRET_SNOWFLAKE_PASS: ${{ secrets.SNOWFLAKE_PASS }}