dragondrop docs
dragondrop.cloud
  • Welcome
  • Getting Started
    • How dragondrop Works
    • 🔒Security
    • Self-Hosted Runners
    • Cloud Perch - Cloud Footprint Visualizations
    • Jobs
      • What is a Job?
      • How Many Jobs Should We Use?
      • Creating a Job
      • Running a Job
      • Managed Drift Only Mode
      • Job Output
    • Setting Up CI/CD
    • Supported Tech Stack
    • Signing Up
    • Schedule a Demo
  • Deploying To Your Cloud
    • Infrastructure Requirements
      • Requirements
      • AWS
      • Azure
      • GCP
    • Environment Variables
    • Updating HTTPS Job Endpoints
    • FAQs
  • Setting Up CI/CD
    • GitHub Action
  • Pricing & Plans
    • Plans
    • FAQs
  • Trouble Shooting
    • Resource Coverage
      • AWS
      • Azure
      • GCP
    • Contact Support
Powered by GitBook
On this page
  • Terraform post-1.5.0
  • Terraform pre-1.5.0
Edit on GitHub
  1. Getting Started

Setting Up CI/CD

PreviousJob OutputNextSupported Tech Stack

Last updated 1 year ago

Terraform post-1.5.0

We strongly recommend running managed cloud-concierge instances with Terraform 1.5 specified.

In this case, cloud-concierge writes import statements using , and allowing you to use your existing Terraform CI/CD deployment pipeline to run resource imports.

Terraform pre-1.5.0

If the Terraform version is specified to be less than version 1.5, then cloud-concierge outputs a series of import statements corresponding to each identified resource that is outside of Terraform control. These can be run manually on the CLI, or our allows for a programatic plan and apply workflow of the generated import statements.

Terraform 1.5+'s native import block
Github action