VCS Providers

Reading time: 4-6 minutes

VCS providers enable Scalr to access Terraform configurations and OPA policies held in a Version Control System (VCS) such as Github, Gitlab, Bitbucket, and Azure DevOps.

• A VCS provider is the Application ID/Key that is generated for an OAuth Application in the VCS system.

• VCS Providers can be created in the account and in environments. Account level VCS providers are available to all environments in the account.

Currently supported VCS’s:

• Github SaaS

• Github Enterprise

• Gitlab SaaS

• Gitlab CE/EE

• Azure Devops Services

• Bitbucket cloud

VCS Provider Configuration

The process is the same for all VCS types.

• Click “New VCS Provider” in the VCS screen

• Select the type and click on “register a new OAuth application” to be taken to the VCS system

• Create the OAuth application and copy the ID/key and secret

• Paste the key and secret into Scalr and save.

Specific instructions for each the VCS types are available via the links below.

• Github

• Gitlab

• Azure Devops Services

• Bitbucket

Github

A Github VCS Provider is authenticated against an OAuth application.

1. Create new VCS Provider and select Github or Github Enterprise from the “Type” drop down

   

Note

For Github Enterprise enter the URL of the Github system.

2. Copy the callback URL, click the “register a new OAuth application” link and register a new OAuth app in Github

   

3. Copy the client ID and client secret and go back to Scalr

   

4. On clicking “create” a redirection back to Github occurs to complete the authorization.

---

Gitlab

A Gitlab VCS provider is authenticated against an OAuth application.

1. Create new VCS Provider and select Gitlab or Gitlab CE/EE from the “Type” drop down

   

Note

For Gitlab CE/EE enter the URL of the Gitlab system.

2. Copy the callback URL, click the “register a new OAuth application” link and register a new OAuth app in Gitlab

   • Check the following options

     • Confidential

     • api

     • read_repository

     • profile

       

     • Allow requests to the local network from web hooks and services

     • Allow requests to the local network from system hooks

       

3. Save and then copy Application ID and Secret

   

4. Go back to IaCP, enter the Id and secret

   

5. On clicking “create” a redirection back to Gitlab occurs to complete the authorization.

---

Azure Devops Services

An Azure Devops Services VCS provider is authenticated against an OAuth application.

1. Create new VCS Provider and select Azure Devops Services from the “Type” drop down

   

2. Copy the callback URL, click the “register a new OAuth application” link and register a new OAuth app in Azure Devops

   • Below is an example app configuration

   • Only two scopes are required for Scalr, Code (read) and Code (status)

     

3. Click Create and then copy the Application ID and Client Secret

   

4. Go back to IaCP, enter the Id and secret

   

5. On clicking “create” a redirection back to Azure Devops occurs to complete the authorization.

---

Bitbucket

A Bitbucket VCS provider is authenticated against an OAuth application.

1. Create new VCS Provider and select Bitbucket from the “Type” drop down

   

2. Copy the callback URL

3. Login to Bitbucket in a new window and register a new OAuth consumer (Settings –> OAuth)

   • Copy in the call back URL

   • Set the permissions as shown below

     

4. Click Save and then copy the Application ID and Client Secret

   

4. Go back to IaCP, enter the Id and secret

   

5. On clicking “create” a redirection back to Bitbucket occurs to complete the authorization.