Terraform

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

The default behavior of terraform fmt is to only output the names of files which have been modified/formatted, but the default behavior of terragrunt hclfmt is to output the paths of all files checked (at terragrunt-log-level info). The latter can end up ou

Version Infracost v0.9.9. We should be able to lookup the filters used in the google_container_registry resource to see what's changed, the golden test files aren't picking this up so it might be related to the region being used.

Terraform resource:

resource "google_container_registry" "registry" {
  project   = var.project_id
}

Actual output, notice the first line is showing

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

Describe the bug
Check: CKV2_AWS_1: "Ensure that all NACL are attached to subnets"
FAILED for resource: aws_network_acl.elasticache
File: /tfplan.json:2623-2683
Guide: https://docs.bridgecrew.io/docs/ensure-that-all-nacl-are-attached-to-subnets

2624 |               "values": {
2625 |                 "arn": "arn:aws:ec2:us-east-1:907320361432:network-acl/acl-0ed5xxxx42a675e",
2626 |

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

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

• 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

Description
For the non-deep mode, which is the default driftctl scan command, we display every time all the information about "unmanaged", "deleted", "drifted", "managed" resources, and the coverage.

It's quite unhelpful here to display the "drifted" resources since it would be ALL THE TIME equal to 0.

Example

Found 14 resource(s)
 - 21% coverage
 - 3 resource(s) managed