Skip to main content
Book a demo

Connect dbt to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add dbt 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 dbt in Runlayer

    Add dbt 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 dbt’s 42 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to dbt

    Sign in the way dbt requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use dbt from GitHub Copilot

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

Tools

42 dbt tools in GitHub Copilot

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

  • Cancel job run

    Cancel a currently running or queued dbt run.

  • Get all macros

    Get the name, description, and package name of all dbt macros in the environment.

  • Get all models

    Get the name and description of all dbt models in the environment.

  • Get all sources

    Get the name, description, and metadata of all dbt sources in the environment.

  • Get dimension values

    Get the distinct values for a given dimension, optionally scoped to specific metrics.

  • Get dimensions

    Get the dimensions for specified metrics

  • Get entities

    Get the entities for specified metrics

  • Get exposure details

    DEPRECATED — use get_node_details instead.

See all 42 dbt tools

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 dbt 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