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
Edit on GitHub
  1. Getting Started
  2. Jobs

Managed Drift Only Mode

For Organizations Using Multiple IaC Tools

PreviousRunning a JobNextJob Output

Last updated 1 year ago

Many organizations settle on a single IaC tool, and work to codify everything using that tool. dragondrop enables for Terraform in a highly-automated process.

Some organizations, however, use different IaC tools to manage different parts of their infrastructure. This may be due to a variety of reasons. Primarily, however, we see organizations with cloud resources that historically have been managed by other tools (think: Azure ARM templates, Cloud Formation, and Ansible).

In such cases, there is good reason not to try and import cloud resources already managed by other tools. , for this reason, supports running drift detection only for resources already managed by Terraform.

Managed Drift Only Mode

Running in Managed-Drift only mode is easy, simply select it in your 's configuration:

cloud-concierge
Job
cloud codification
Example of Job configuration, selected to only detect drift in Terraform-managed resources.