Skip to main content
Book a demo

Connect Snowflake to GitHub Copilot

Give GitHub Copilot governed access to Snowflake’s 8 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot setup guide

Set up

Add Snowflake to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Approve Snowflake in Runlayer

    Add Snowflake from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Snowflake’s 8 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Snowflake

    Each user signs in to Snowflake with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Snowflake from GitHub Copilot

    Snowflake’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.

Tools

8 Snowflake tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • Describe semantic view

    Describe a semantic view.

  • Get semantic view ddl

    Get the DDL for a semantic view.

  • List semantic views

    List all semantic views in the account, database, or schema.

  • Query semantic view

    Writes and runs a statement to query a semantic view using DIMENSIONS, METRICS, and/or FACTS.

  • Run Snowflake query

    Run a SQL query in Snowflake.

  • Show semantic dimensions

    Show all semantic dimensions in the account, database, or schema.

  • Show semantic metrics

    Show all semantic metrics in the account, database, or schema.

  • Write semantic view query tool

    Writes a query statement to query a semantic view using DIMENSIONS, METRICS, and/or FACTS.

Control

What Runlayer can see and stop in GitHub Copilot

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.

  • Gateway policy (available)

    Every Snowflake call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination