Terraform Version

Terraform v0.12.28
+ provider.google v3.28.0

Terraform Configuration Files

# ./main.tf
module "project" {
  source          = "../../../../blueprints/gcp/project"
  billing_account = "002A75-ABB3C9-680D62"
  folder_id       = "746484843613"
  project_id      = "di-test-mod-gcp-project-1"
  owner           = "owner@example.com"

  

Description
Python 2 Deprecation FAQ is showing twice on the right navigation

Suggested Fix
Is this a duplicate on the index and then it is also pulling it into view from the .rst file? Unsure, but it looks incorrect.

**Type of documentati

• AWS::CloudFormation::Stack
• AWS::Cognito::UserPool
• AWS::DocDB::DBInstance
• AWS::EC2::Volume
• AWS::Elasticsearch::Domain
• AWS::FSx::FileSystem
• AWS::SQS::Queue

This is 🐛 Bug Report

Requesting that you add the new Gitlab Provider as a new VCS Provider.

See here for the provider details: https://registry.terraform.io/providers/gitlabhq/gitlab/latest

Describe the bug
This resource causes the error WARNING: skipped AWS017 check due to error(s): value is null

And it happens even if I try to explicit skip AWS017 from cli:

tfsec --exclude AWS017
WARNING: skipped AWS017 check due to error(s): value is null

tfs

For example-

infracost/infracost:1.0.1-tf0.12.26, infracost/infracost:1.0.1-tf0.13.1

Hi, I just created a new environment (test2) for my app, and now I’m trying to deploy a service to that environment but it fails.

Just for context, I’m attempting to use a monorepo setup:

• My apps (services) are in /apps/
• My copilot manifests etc are in /infrastructure/copilot/
• I always run copilot from /infrastructure/
• Each manifest has an image property that points to

• terrascan version: 1.2
• Operating System: all

Description

When scanning a repo, if the severity field is not all caps (HIGH|MEDIUM|LOW), when violations are output, the color of the severity field does not show up. The compare should be case-insensitive, OR we can normalize the severity field.

What I Did

terrascan scan -d [dir]

Garbage collection works by listing everything with the gc-tag. In a busy cluster, we really want that filter to happen server-side and ideally using an index of some sort.

That means we should use a Kubernetes label, not an annotation.

I think this will require a two-step migration plan (write both but continue to read annotation; release; drop support for annotation; release).