setup-terraform VS atlantis

# Adaptation of the https://developer.hashicorp.com/terraform/tutorials/automation/github-actions workflow Name: TerraformMainBranch SchemaVersion: "1.0" # Here we are including the trigger for this workflow: Push / Pull Request. If not included then this workflow will be executed only manually Triggers: - Type: Push Branches: - main # Here we are defining the actions that will be executed for this workflow Actions: Terraform-Main-Branch-Apply: Identifier: aws/build@v1 Inputs: Sources: - WorkflowSource Environment: Connections: - Role: Main-Branch-Infrastructure Name: "XXXXXXXXXXXX" Name: TerraformBootstrap Configuration: Steps: - Run: export TF_VERSION=1.5.2 && wget -O terraform.zip "https://releases.hashicorp.com/terraform/${TF_VERSION}/terraform_${TF_VERSION}_linux_amd64.zip" - Run: unzip terraform.zip && rm terraform.zip && mv terraform /usr/bin/terraform && chmod +x /usr/bin/terraform - Run: terraform init -no-color - Run: terraform validate -no-color - Run: terraform plan -no-color -input=false - Run: terraform apply -auto-approve -no-color -input=false Compute: Type: EC2

Now, there is a GitHub issue for setup-terraform that essentially demonstrates a problem that might occur if you try to reference your Git repo from Azure Pipelines (using HTTP) without appropriate permissions or workarounds. In this issue, there are two solutions:

Have you tried the official tutorial here: https://learn.hashicorp.com/tutorials/terraform/github-actions ?

Think of a simple web application you could build and deploy into a cloud environment like aws or GCP. Build your cloud infrastructure with Terraform for this application. Deploy that infrastructure and the application itself using GitOps. For example this: https://learn.hashicorp.com/tutorials/terraform/github-actions

Here's an example using Github Actions: https://learn.hashicorp.com/tutorials/terraform/github-actions. You can set all kinds of conditions in the pipeline config to only trigger on certain dirs or files, like (Github Action example:

You may need to use the Terraform Cloud. When you use the Terraform Cloud, please use this guide. However, it's not required for now.

Since it sounds like you're using GitHub, using GitHub Actions for any CI pipelines would be easiest. You could run terraform plan in your PRs, there's a great writeup on how to do it here. Or any unit tests, docker builds, etc. Lots of great ideas at Awesome Actions.

#11-15 The Finish Line So for the last portion of the challenge, I had to implement a test against my python code to make sure that it works as it should every time I update it. I then realized I wish I had started here first since I'd need to use IaC to deploy and configure all my resources. Reading I found that I could use SAM but instead I used Terraform/Terraform Cloud since I remember that's what many people use. I tore down almost everything that I did in the AWS console and redid everything using Terraform. I had to setup the API tokens, make a variable set using my AWS credentials and followed the tutorial on how to setup github actions and then I applied it to this challenge. I also used this resource to make a simple test. After that it was just setting up repositories for both my back end and front end.

None of these are a replacement of Terraform Cloud (recently rebranded to HCP Terraform). For example, when you create a PR, it could affect multiple workspaces. The new experimental version of TFC/TFE (I refuse to call it HCP!) implements Stacks, which is something like a workflow, and links one workspace output to other workspace inputs. None of the open-source solutions, including the paid Digger [0], support this - only the paid one, such as Spacelift [1] (which is the closest to TFC if you ask me). Having a monorepo of Terraform is a common design pattern, so, if I change an embedded module, it could trigger changes it many workspaces. As far as I know, Atlantis [2] can't really help in this case.

By the way, the reason I singled-out Spacelift is due to its quality, and the great Terraform provider it has. Scalr [3], for example, has a really low-quality Terraform provider. I extensively use the hashicorp/tfe provider to manage TFC itself.

[0]: https://digger.dev/

[1]: https://spacelift.io/

[2]: https://www.runatlantis.io/

[3]: https://www.scalr.com/

Atlantis is a pull request automation tool that works well with plain Terraform right away. But what if we're already using Terramate to generate Terraform code?

Atlantis automates reviewing and deploying Terraform via pull requests, streamlining collaboration and ensuring consistency across Terraform deployments.

For example, Atlantisgo for Terraform, Zapier’s Kubechecks for Argo CD, Quizlet’s GitHub action all do something similar to this. But a generic, extensible tool for IaC providers doesn’t seem to exist. Additionally, many of them require exposing your Kubernetes cluster or other infrastructure to third-party access, webhooks, etc.

Our first attempt was to introduce other engineering teams to Terraform - the Platform team was already using it extensively with Terragrunt, and using Atlantis to automate plan and apply operations in a Git flow to ensure infrastructure was consistent. We'd written modules, with documentation, and an engineer would simply need to raise a PR to use the module and provide the right values, and Atlantis (once the PR was approved by Platform) would go ahead and set it up for them.

Alternatively, you can look at solutions like Atlantis or spacelift.

Atlantis: https://www.runatlantis.io/

Looking at the commits at https://github.com/runatlantis/atlantis, it looks like 1.6.5. Am I right?

We use Atlantis [0] for CI/CD automation of Terraform pull requests to a centralized repository. It's pretty good too, especially for a self-hosted solution. I can't see how Terraform Cloud's costs would be justifiable for us without a custom contract.

[0] https://www.runatlantis.io/