snowflake-connections

This skill provides a centralized approach to managing Snowflake connection configurations using the connections.toml file format, which is essential for modern data engineering workflows involving Snowflake CLI, Streamlit applications, and Snowpark pipelines. It is designed for data engineers, developers, and platform administrators who need to securely manage connectivity across multiple environments such as development, staging, and production. The skill guides users through the technical specifications of connection parameters, including account identifiers, warehouse assignments, database contexts, and schema routing, ensuring that applications interact with the correct data infrastructure consistently.

• Support for multiple authentication methods: External browser (SSO), key pair (snowflake_jwt), username/password, and OAuth tokens.

• Configuration management for connections.toml file located at ~/.snowflake/connections.toml or %USERPROFILE%/.snowflake/connections.toml.

• Guidance on managing multi-environment configurations using profile blocks to easily switch between dev, staging, and production.

• Security best practices, including recommendations for encrypted key pair storage and rotation, avoidance of hardcoded credentials, and the usage of environment variables for sensitivity.

• Troubleshooting assistance for authentication errors, connection timeouts, and MFA-related issues.

• Integration patterns for automated CI/CD pipelines, emphasizing the use of key pair authentication for headless environments.

• Users should use this skill for setting up local development environments, containerized applications, or CI/CD runner configurations.

• Note that while authentication principles are consistent with dbt, this skill specifically addresses connections.toml; for dbt-specific profiles.yml, please refer to the dbt-core skill.

• Input expected includes configuration parameters, environment requirements, or error messages related to connectivity.

• Output typically results in validated connection configurations, structured toml snippets, or step-by-step resolution for access issues.

• Constraints: Strictly for Snowflake-native connection management; does not cover general network firewall or proxy configurations.