Prerequisites: At this point, you should have gotten access to Terraform Enterprise, and created an organization if necessary.
Before you can use TFE, it needs access to the version control system (VCS) you use for Terraform code.
» About VCS Access
Most workspaces in TFE are associated with a VCS repository, which provides Terraform configurations for that workspace. To find out which repos are available, access their contents, and create webhooks, TFE needs access to your VCS service.
Although TFE's API lets you create workspaces and push configurations to them without a VCS connection, the primary workflow expects every workspace to be backed by a repository. If you plan to use TFE's GUI to create workspaces, you must configure VCS access first.
» Configuring GitHub Access
Connecting TFE to your VCS involves five steps:
|On your VCS||On TFE|
|Register your TFE organization as a new app. Get ID and key.|
|Tell TFE how to reach VCS, and provide ID and key. Get callback URL.|
|Provide callback URL.|
|Request VCS access.|
|Approve access request.|
The rest of this page explains the GitHub versions of these steps.
Note: Alternately, you can skip the OAuth configuration process and authenticate with a personal access token. This requires using TFE's API. For details, see the OAuth Clients API page.
» Step 1: On GitHub, Create a New OAuth Application
- Open github.com in your browser and log in as whichever account you want TFE to act as. For most organizations this should be a dedicated service user, but a personal account will also work.
Important: The account you use for connecting TFE must have admin access to any shared repositories of Terraform configurations, since creating webhooks requires admin permissions.
- Navigate to GitHub's Register a New OAuth Application page.
This page is located at https://github.com/settings/applications/new. You can also reach it through GitHub's menus:
- In the upper right corner, click your profile picture and choose "Settings."
- In the navigation sidebar, click "Developer settings," then make sure you're on the "OAuth Apps" page (not "GitHub Apps").
- In the upper right corner, click the "New OAuth App" button.
- This page has a form with four text fields.
Fill them in as follows:
| Field name | Value |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Application Name | Terraform Enterprise (
<YOUR ORGANIZATION NAME>) |
| Homepage URL |
https://app.terraform.io (or the URL of your private TFE install) |
| Application Description | Any description of your choice. |
| Authorization callback URL |
https://example.com/replace-this-later (or any placeholder; the correct URI doesn't exist until the next step.) |
Click the "Register application" button, which creates the application and takes you to its page.
Download this image of the Terraform logo, upload it with the "Upload new logo" button or the drag-and-drop target, and set the badge background color to
#5C4EE5. This optional step helps you identify TFE's pull request checks at a glance.
Leave this page open in a browser tab. In the next step, you will copy and paste the unique Client ID and Client Secret.
» Step 2: On TFE, Add a VCS Provider
- Open TFE in your browser and navigate to the "VCS Provider" settings for your organization. Click the "Add VCS Provider" button.
If you just created your organization, you might already be on this page. Otherwise:
- Click the upper-left organization menu, making sure it currently shows your organization.
- Click the "Settings" link at the top of the page (or within the ☰ menu)
- On the next page, click "VCS Provider" in the left sidebar.
Click the "Add VCS Provider" button.
- The next page has a drop-down and four text fields. Select "GitHub.com" from the drop-down, and enter the Client ID and Client Secret from the previous step. (Ignore the two disabled URL fields, which are used for on-premise VCSs.)
Click "Create VCS Provider." This will take you back to the VCS Provider page, which now includes your new GitHub client.
Locate the new client's "Callback URL," and copy it to your clipboard; you'll paste it in the next step. Leave this page open in a browser tab.
» Step 3: On GitHub, Update the Callback URL
Go back to your GitHub browser tab. (If you accidentally closed it, you can reach your OAuth app page through the menus: use the upper right menu > Settings > Developer settings > OAuth Apps > "Terraform Enterprise (
<YOUR ORG NAME>)".)
In the "Authorization Callback URL" field, near the bottom of the page, paste the callback URL from TFE's OAuth Configuration page, replacing the "example.com" placeholder you entered earlier.
Click the "Update application" button. A banner saying the update succeeded should appear at the top of the page.
» Step 4: On TFE, Request Access
- Go back to your TFE browser tab and click the "Connect organization
<NAME>" button on the VCS Provider page.
This takes you to a page on github.com, asking whether you want to authorize the app.
- The authorization page lists any GitHub organizations this account belongs to. If there is a "Request" button next to the organization that owns your Terraform code repositories, click it now. Note that you need to do this even if you are only connecting workspaces to private forks of repositories in those organizations since those forks are subject to the organization's access restrictions. See About OAuth App access restrictions.
- Click the green "Authorize
<GITHUB USER>" button at the bottom of the authorization page. GitHub might request your password to confirm the operation.
» Step 5: Contact Your GitHub Organization Admins
If your organization uses OAuth app access restrictions, you had to click a "Request" button when authorizing TFE, which sent an automated email to the administrators of your GitHub organization. An administrator must approve the request before TFE can access your organization's shared repositories.
If you're a GitHub administrator, check your email now and respond to the request; otherwise, contact whoever is responsible for GitHub accounts in your organization, and wait for confirmation that they've approved your request.