VCS Providers

Note

VCS providers can be created and managed as code through the Scalr Terraform Provider.

VCS providers enable Scalr to access Terraform configuration files and OPA policies held in a version control system (VCS) such as Github, Gitlab, Bitbucket, and Azure DevOps. VCS providers are required if a GitOps model is desired. There is no extra configuration needed for Scalr to send checks back to VCS providers during the pull request process. VCS providers can be created at the account and/or the environment scopes. If created at the account scope, the VCS provider will be made available to all environments within the account.

Currently supported VCS’s:

GitHub SaaS
GitHub Enterprise
GitLab SaaS
GitLab CE/EE
Azure DevOps Services
Bitbucket Cloud
Bitbucket Data Center

To configure new VCS providers go to the “VCS provider” or “VCS” menu option and click “New VCS Provider”

Github

A Github VCS Provider is authenticated against an OAuth application.

1. Click Github or Github Enterprise and enter the provider name and, for Enterprise, the URL.

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

3. Click on “Generate a new client secret and copy the client ID and client secret.

4. Go back to Scalr and paste the values into the form

5. 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. Click Gitlab or Gitlab Enterprise and enter the provider name and, for Enterprise, the URL

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

   • Enable the following permissions in the application configuration:

     • Confidential

     • api

     • read_repository

     • profile

• For Gitlab Enterprise check these options in the network settings (Admin Area):

  • 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 Scalr, 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. Click Azure Devops Services and enter the provider name.

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 Scalr, enter the Id and secret

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

---

Bitbucket Cloud

A Bitbucket Cloud VCS provider is authenticated against an OAuth application.

1. Click Bitbucket and enter the provider name.

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

5. Go back to Scalr, enter the Id and secret

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

---

Bitbucket Data Center

A Bitbucket Data Center VCS provider is authenticated using a personal access token.

1. Click Bitbucket Data Center and enter the provider name and URL of Bitbucket.

2. Login to Bitbucket Data Center by clicking on the link provided and create a new personal access token.

   • Set the permissions as shown below

3. Click Create and then copy the token

4. Go back to Scalr, enter the token and click “Create”.