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. Setting Up CI/CD

GitHub Action

CI/CD Support within GitHub Actions Pipelines.

PreviousFAQsNextPlans

Last updated 1 year ago

Note: You can if running your managed cloud-concierge containers with Terraform v1.5.0 or greater

Set up our within the code repositories in which dragondrop will be opening Pull Requests. but at a high-level the CI/CD job performs the following operations:

  • Install your desired version of Terraform

  • If in plan mode, check to make sure that the only changes to Terraform in the current pull request are to import external resources into Terraform control, and that those imports are correctly specified.

  • If in apply mode, perform everything from the plan step and then run the import statements as code.

We recommend using plan mode during continuous integration, and after merge, use apply mode.

Given that some of the needed environment variables are a bit involved, we also offer support for auto-validation within the web application. This allows faster cycle time in making sure your environment variables are correctly formatted. All environment variables are evaluated client-side.

For further details on implementing the Action itself, the README associated with the Action is well documented.

GitHub Action
skip this section