terraform-up-and-running-code VS setup-terraform

Terraform: Up & Running. O'Reilly Media, Brikman, Y.

There’s a new edition of Terraform: Up & Running that was published last year.

Terraform: Up and Running - Excellent read on using Terraform

If you’re looking for general terraform this is your best bet https://www.terraformupandrunning.com

You should also check this out : https://github.com/brikis98/terraform-up-and-running-code/tree/3rd-edition. Its the companion repo to an actual book which i recommend as well but this series of blog posts by the author maps to the first five chapters of the book so you can explore and see if you want to splurge for the book.

OP, do this, I'm going through the 3rd edition right now to evaluate it as a teaching tool for my colleagues and all examples are up to date and his explanation style is fantastic. You can see he even made some recent updates to the repo 3 days ago: https://github.com/brikis98/terraform-up-and-running-code

# 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.