Skip to main content

Connect DX Data Cloud to GitHub Copilot

Give GitHub Copilot governed access to DX Data Cloud’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add DX Data Cloud 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 DX Data Cloud in Runlayer

    Add DX Data Cloud 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 DX Data Cloud’s 10 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to DX Data Cloud

    An admin adds DX Data Cloud credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use DX Data Cloud from GitHub Copilot

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

Tools

10 DX Data Cloud tools in GitHub Copilot

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

  • Get entity details

    Get comprehensive details about a specific entity including its information, tasks, and scorecards - we can use this to check operational readiness/health of an entity.

  • Get initiative details

    Get initiative details including both the initiative info and its progress report.

  • Get scorecard info

    Retrieve details about a specific scorecard, including its defined levels and checks.

  • Get team details

    Retrieve details for an individual team.

  • List entities

    List entities from the DX software catalog.

  • List initiatives

    Lists all initiatives with summary information.

  • List scorecards

    List all active scorecards.

  • List teams

    List all teams in DX.

See all 10 DX Data Cloud 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 DX Data Cloud 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