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"

  

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

I'm using disable_init to prevent terragrunt from accessing remote state bucket on its own (reason explained below). However, this also disables initializing the backend by terraform: it passes -backend=false to terraform init. As a result, the backend is not initialized and all terragrunt commands result in errors:

$ terragrunt plan
...
[terragrunt] [/tf] 2020/11/11 21:14:49 Running c

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

centos 8.2 已经发布了，想了解下对 centos 8.x 的支持计划大概是怎样的，谢谢。

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

There's a formatting specification for Tag Keys and Values. One issue with applying some changes is that you are disallowed from using certain characters (notably the ,) in a Tag Value, and this is not being caught by tflint currently.

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-resource-tags.html#w2ab1c25c10d254c13c17

Check to confirm CloudTrail is configured for multi-region.

CloudFormation - IsMultiRegionTrail: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudtrail-trail.html

Feature request

support configurable Kubernetes service IP address range

What is the current behavior?

configurable Kubernetes service IP address range is not supported

What is the expected behavior?

Support this feature ( for reference CFN - https://docs

For example-

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

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions