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

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, they generate extra noise for issue followers and do

I am having a project structure as follows:
.
├── README.md
├── modules
│ ├── function-app-consumption
│ │ ├── locals.tf
│ │ ├── main.tf
│ │ ├── output.tf
│ │ └── variables.tf
│ └── storage-account
│ ├── main.tf
│ ├── output.tf
│ └── variables.tf
└── sandbox
├── eastus
│ ├── regional.tfvars
│ ├── functionapp-svc
│ │ └─

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 的支持计划大概是怎样的，谢谢。

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 "me too" comments, they generate extra noise for issue followers and

See infracost/infracost#287 for a previous attempt

Describe the bug
CKV_GCP_14 requires a backup configuration, but it does not take into consideration read replicas.
A read replica cannot have backup enabled in GCP.

To Reproduce
Steps to reproduce the behavior:

1. Create a google_sql_database_instance with master_instance_name and replica_configuration
2. Chekov will pop up error CKV_GCP_14

Expected behavior
Read replicas

PR o'clock

Description

Please explain the changes you made here and link to any relevant issues.

Not a big issue but when generating a plan on mac vs linux yamlencode generates different output. This function is still experimental and may change in the future, for a consistent output we could use jsonencode until yamlencode is ready.

linux:

![image](https://user-images.gi

It'd be good to have a consistent warning for the case where no provider constructs were generated in .gen

Example: