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

Following example in the documentation:

resource "aws_db_proxy_target" "example" {
  db_instance_identifier = aws_db_instance.example.id
  db_proxy_name          = aws_db_proxy.example.db_proxy_name
  target_group_name      = aws_db_proxy_default_target_group.example.name
}

fails with an exception:

Error: Unsupported attribute

  on ../modules/rds/main.tf line 34, in resour

I'm currently working on a project where I have a number of different modules which make up our web application stack. We have many of these stacks defined, all of which pull from a set of top-level .hcl terragrunt files (one for each module). Some of these modules are optional for a given stack, in my case for example whether or not to enable AzureAD single sign-on is an optional, and is defined

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
The RDS checks in tfsec do not detect issues in usage of the RDS module available at: https://registry.terraform.io/modules/terraform-aws-modules/rds/aws/latest

To Reproduce
Steps to reproduce the behaviour:

1. Create the following terraform file:

module "db" {
  source = "terraform-aws-modules/rds/aws"
  version = "~> 2.0"

  identifier = "demodb"

Do not allow action “*” or resources “*” in an IOT Policy

Example policies are here: https://docs.aws.amazon.com/iot/latest/developerguide/example-iot-policies.html

https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-iot-policy.html
https://www.terraform.io/docs/providers/aws/r/iot_policy.html

For example-

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

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

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