snowflake-connections

Configure Snowflake connections by setting up connections.toml (CLI, Streamlit, Snowpark) and profiles.yml (dbt) with account, user, warehouse, database, schema, and role fields. Place connections.toml in ~/.snowflake/ on Linux/Mac or %APPDATA%\.snowflake\ on Windows. Choose your authentication method—SSO, key pair, username/password, or OAuth—and add credentials to the appropriate config file.

Snowflake supports four authentication methods: SSO/external browser, key pair authentication (with optional passphrase), username/password, and OAuth tokens. Key pair is recommended for production and CI/CD workflows. Each method configures differently in connections.toml; key pair requires private_key_path and optional private_key_passphrase fields.

Yes. Environment variable overrides let you dynamically change connection parameters without modifying config files, making multi-environment deployments (development, staging, production) easier. Override specific fields like warehouse or role per environment while keeping base credentials in connections.toml.

Define multiple connection profiles in connections.toml or profiles.yml with distinct names and settings for each environment. Specify the target profile when connecting from CLI, Streamlit, or dbt. Use environment variable overrides or profile selection to switch between development, staging, and production without changing files.

Store private keys securely outside your repository, use key passphrases for encryption, rotate keys regularly, and never commit credentials to version control. For CI/CD, inject private keys via secrets management tools. Restrict file permissions on private_key_path to prevent unauthorized access.

This Skill consolidates configuration guidance for multiple tools (CLI, Streamlit, Snowpark, dbt), covers all authentication methods, handles multi-environment setup, and includes security best practices and troubleshooting. It eliminates guesswork on file paths, required fields, and credential rotation across tools.