CI/CD & Terraform Runners

Support Terraform Integrations

In order for Resourcely to verify infrastructure resource definitions and guardrails, it must run alongside your CI/CD pipeline.

Resourcely works with Terraform in order to validate infrastructure guardrails and prevent misconfigurations. Terraform must run in your repository in order to create plans that Resourcely will validate. The following is required in order to get started with using Terraform:

• A Terraform solution to integrate into your version control system (GitHub/GitLab)

• Terraform provider definitions within the repository used for infrastructure provisioning

Resourcely is designed with data privacy in mind and does not transmit terraform plans to our servers, as they may contain sensitive information.

Terraform Integration

A method of running Terraform on your repository and creating Terraform plans is required in order to get started. See below for Configuration options for different Terraform solutions:

Atlantis🐟AWS CodeBuild🎏GitHub Actions🦊GitLab Pipelines🗻HashiCorp Cloud Platform (formerly Terraform Cloud)🌎Terrateam🌌Spacelift

Terraform Provider Definitions in Repository

Repositories that will leverage Resourcely require the Terraform providers to be defined and stored within the repository. This is required for a Terraform plan to be generated.

The Terraform provider configuration is usually added to a folder named Terraform within the root of your repository.

See the Terraform documentation to see how to properly configure Terraform providers within your repository:

Provider Configuration - Configuration Language | Terraform | HashiCorp DeveloperProvider Configuration - Configuration Language | Terraform | HashiCorp Developer

Terraform Provider Configuration