Connect Google Compute Engine to GitHub Copilot
Give GitHub Copilot governed access to Google Compute Engine through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Compute Engine to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve Google Compute Engine in Runlayer
Add Google Compute Engine from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Google Compute Engine’s tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to Google Compute Engine
Each user signs in to Google Compute Engine with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use Google Compute Engine from GitHub Copilot
Google Compute Engine’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
Google Compute Engine tools in GitHub Copilot
Google Compute Engine reports its tools when your organization connects it, so the list depends on your deployment.
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 Google Compute Engine 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