Skip to content


terraform logo

Terraform can manage existing and popular service providers, such as AWS, as well as custom in-house solutions.

It uses configuration files to describe the components necessary to run a single application or your entire datacenter.

It generates an execution plan describing what will happen to reach the desired state, and afterwards executes it to build the desired infrastructure. As the configuration changes, Terraform is able to determine the changes and create incremental execution plans which can be applied.

The infrastructure Terraform can manage includes low-level components such as compute instances, storage, and networking, as well as high-level components such as DNS (Domain Name Service) entries, SaaS (Software as a Service) features.

Here are 13,763 public repositories matching this topic...

mkielar commented Jun 15, 2022

Terraform Version

Terraform v1.2.2
on linux_amd64
+ provider v4.18.0
+ provider v3.3.1
+ provider v0.5.1
+ provider v1.7.10

Git version

git version 2.25.4

Terraform Configuration Files

  1. This works, b
bug config good first issue confirmed
eherot commented Jun 28, 2022


The header example for aws_appsync_api_cache seems to have the parameters for aws_appsync_api_key (api_cache does not have an expires parameter).

What it says

resource "aws_appsync_api_cache" "example" {
  api_id  =
  expires = "2018-05-03T04:00:00Z"

What it probably should say

resource "aws_appsync_api_c
documentation good first issue service/appsync
Nek0trkstr commented Mar 6, 2022

Hi, I've set TERRAGRUNT_CONFIG=.terragrunt.hcl.
So my root and leaf folders have this .terragrunt.hcl file.
Everything works well when I'm trying to run terragrunt from child folder, but I get "Could not find any subfolders with Terragrunt configuration files" error when trying to run from terragrunt run-all plan from root. Renaming .terragrunt.hcl -> terragrunt.hcl fixes the issue, but I w

bug good first issue
harishachappa commented Jun 6, 2022

Describe the issue
Checkov skips terraform file when it can't parse a file. When you are using checkov in gitlab ci pipeline with junitxml output, it will be better to include such erros in 'Errors' list instead of ignoring them.


resource "aws_alb" "alb" {
  name                             = "foobar-nlb"
  load_balancer_type               = "network"
good first issue outputs
adegoodyer commented Aug 11, 2021
  • terrascan version: 1.9.0
  • terraform version: 1.0.1

Enhancement Request

Other security scanning tools (e.g. checkov and tfsec) have a --soft-fail flag or equivalent option that allows you to always exit with 0 status.

Extremely useful when running the tool without halting a pipeline for example.

I currently use a workaround, but something more concrete would be very desira

Created by Mitchell Hashimoto, HashiCorp

Released July 28, 2014

Latest release 13 days ago


Related Topics

hashicorp infrastructure infrastructure-as-code