Resourcely Documentation
LoginSign Up
  • Get Started
    • 🎱What is Resourcely?
    • 👋Why Resourcely
    • 🏃Quickstart
      • Terraform policies integrated into CI
      • Remediate policy violations in existing infrastructure
      • Templates for generating Terraform
      • Glossary
  • Concepts
    • Foundry
      • Create Blueprints with Foundry
      • Creating Guardrails with Foundry
      • lmport Terraform Modules
    • Guardrails
      • Writing your own Guardrails
      • Editing Guardrails
      • Releasing Guardrails
      • Enabling Inactive Guardrails
      • Guardrails in Action
        • 🐱GitHub Actions
        • 🦊GitLab Pipelines
    • Campaigns
      • Get started with Campaigns
      • Creating Campaigns
      • Remediate Resources
      • Campaign Agent
        • State File Support
          • Amazon Simple Storage Service (S3)
          • Google Cloud Storage (GCS)
          • HCP Terraform
          • Spacelift
        • Running Campaigns with GitHub Actions and a Repo-Hosted State File
        • Running Campaigns Locally
    • Blueprints
      • Authoring Your Own Blueprints
      • Using Built-in Resourcely Blueprints
      • Configuring Global Contexts
      • Deep Linking
    • Resources
      • Provisioning Infrastructure
      • Editing Infrastructure
      • Shopping Cart
      • Config Roots and Environments
    • Other Features and Settings
      • Global Values
      • Global Context
      • Metrics
      • Resourcely-cli
      • Resourcely.yaml
      • VCS Proxy
      • Settings
        • User management
        • Company Information
        • Notification Settings
        • Change Management
          • 🐱Connect to GitHub
          • 🦊Connect to Gitlab
        • Generate API Token
    • ✨Production Setup
      • Single Sign-On (SSO)
        • Auth0
        • AWS Single Sign-On
        • Azure AD
        • Google Workspace
        • JumpCloud
        • Okta
        • Omnissa Workspace ONE (formerly VMware)
        • OneLogin
        • Ping Identity
        • Other SAML / OIDC Providers
      • Source Code Management
        • Page
        • 🐱GitHub
        • 🦊GitLab
        • Atlassian Bitbucket
        • Azure Repos
  • Tutorials and guides
    • Remediation Use Cases
      • Apply tags to resources for automating backups
      • Implement centralized logging
    • Blueprints Use Cases
      • Automate Data Pipeline Creation
      • Encryption for GCP
      • AWS Account Factory
      • Streamline and govern AI
      • IAM Factory
      • Cost optimization for FinOps
      • Guardrails for Terraform Modules
    • Using the Resourcely Terraform Provider
      • Setup Resourcely Provider
      • Blueprints
      • Guardrails
      • Global Context
  • Integrate
    • CI/CD & Terraform Runners
      • Atlantis
      • 🐟AWS CodeBuild
      • Azure Pipelines
      • Buildkite
      • CircleCI
      • CloudBees CI
      • Codefresh
      • Digger
      • Env0
      • 🎏GitHub Actions
        • 🐱Local Plan
          • 🐹AWS with OpenID Connect
        • 🐶Terraform Cloud Integration
      • 🦊GitLab Pipelines
      • Harness
      • 🗻HashiCorp Cloud Platform (formerly Terraform Cloud)
      • Jenkins
      • Octopus Deploy
      • Scalr
      • 🌌Spacelift
      • Terramate
      • 🌎Terrateam
    • Cloud Providers
      • 🌨️Amazon Web Services (AWS)
      • 🤓Google Cloud Platform (GCP)
        • Guardrail Gaunlet at Google Cloud Next 2025
      • 💾Microsoft Azure
      • Alibaba Cloud
      • Huawei Cloud
      • IBM Cloud
      • Oracle Cloud Infrastructure (OCI)
      • Tencent Cloud
      • VMware vSphere
    • Developer Portals
      • Atlassian Compass
      • Backstage
      • Cortex
      • Harness IDP
      • Home grown internal developer portals
      • OpsLevel
      • Port
      • Roadie
    • ITSM
      • Atlassian Jira
      • FreshWorks
      • ServiceNow ITSM
      • ZenDesk
    • CSPM
      • Wiz
    • More Terraform Provider Integrations
      • 🚂ConductorOne Provider
      • Databricks Provider
      • Kubernetes Provider
      • 🐕Datadog Provider
      • ❄️Snowflake Provider
Powered by GitBook
On this page
  • Authenticate Resourcely with Gitlab
  • Integrating Resourcely with Gitlab using a Group Access Token
  • Configuring a GitLab Webhook for Resourcely
  • Choosing a Repository for Resourcely to Monitor
  1. Concepts
  2. Other Features and Settings
  3. Settings
  4. Change Management

Connect to Gitlab

Source Code Management (SCM) Integration

PreviousConnect to GitHubNextGenerate API Token

Last updated 1 year ago

Let’s get started with integrating Gitlab with Resourcely. This step entails:

  • Authenticate Resourcely with GitLab

  • Integrating Resourcely with Gitlab using a Group Access Token

  • Configuring a Webhook for Resourcely

  • Choosing a Repository for Resourcely to Monitor

Authenticate Resourcely with Gitlab

Now let's connect Resourcely to Gitlab to enable automatic runs on git commits, automatic runs on merge-requests, and status updates. Press the Connect to Gitlab button to proceed.

For Resourcely to modify Gitlab settings, you must first grant the appropriate level of authorization on your behalf. Press the Authorize with Gitlab button to proceed.

You will then be taken to your Gitlab user settings and asked to Authorize Resourcely to use your account. Press the Authorize button to proceed.

Go back to the Resourcely window and proceed with onboarding.

Integrating Resourcely with Gitlab using a Group Access Token

To grant access to all projects within the Gitlab group a group access token is required. Enter the Group Access Token created as seen in the GitLab prerequisites section. Then press the Continue button to proceed.

The group access token is used by Resourcely to verify the GitLab integration such as verifying the webhook

Configuring a GitLab Webhook for Resourcely

GitLab Webhooks deliver notifications to an external web server whenever a defined event occurs on GitLab. To proceed to configure a GitLab webhook, click on the GitLab webhook Settings link and copy over the Webhook URL and Webhook secret token provided in the following dialogue:

You must then configure the webhook with the following settings:

  • Trigger: Merge request events

All other webhook settings can remain unchanged.

Once the webhook has been properly set up, scroll down to the bottom of the page and press the Add webhook button. You can now see that the webhook was added successfully.

Navigate back to the Resourcely window and press the Continue button to proceed.

Choosing a Repository for Resourcely to Monitor

You must now choose the repository that hosts your Terraform code. This is the repository in which Resourcely will watch for commits and merge-requests.

Press the Add a repository button and select a repository from the dropdown.

You can add more repositories to monitor by pressing the Add repository button.

To begin onboarding, only one repository is needed. However, you have the flexibility to add more later.

Press the Publish button to continue. You should now see that GitLab has been successfully integrated with Resourcely.

Now that Resoucely has been fully integrated into GitLab, we must add the Resourcely CI/CD Job to our project for Resourcely to validate our infrastructure resources. Proceed to Generate API Token

🦊
Configure change management onboarding home
Authorize with GitLab request
Gitlab Resourcely Authorization page
Provide a group access token
Create a GitLab webhook
GitLab Webhook Settings
Active Webhooks
Choose a repository
Select a repository from the list
Repository selected
GitLab integrated into Change Managment