infrastructure-as-code

Description

the docs at https://docs.saltproject.io/en/latest/topics/spm/master.html#update-file-roots show file_roots with numbered lines instead of the list indicator.

file_roots:
  base:
    1. /srv/salt
    2. /srv/spm/salt

Suggested Fix
That should be

file_roots:
  base:
    - /srv/salt
    - /srv/spm/salt

Type of documentation
Salt docum

Trivy was now released with version 0.25.0 but the Helm Chart does still install version 0.24.0.

Are there any objections to bump the version there, too ?

What is the problem?

Unlike the module aws_apigateway where I would just do

const api = new apigateway.RestApi(this, 'hello-api');
const plan = api.addUsagePlan('UsagePlan', {
  name: 'Easy',
  throttle: {
    rateLimit: 10,
    burstLimit: 2
  }
});

there doesnt seem to be an equivalent way of doing this in aws-apigatewayv2-alpha.

Reproduction Steps

I

I suggest adding MongoDB Atlas to the supported cloud as a feather.

Previous discussion:

• infracost/infracost#953
• infracost/infracost#1172 (comment)

Infracost has a method of passing custom flags for when Infracost runs terraform plan, but it doesn't support passing custom flags to terraform init.

This will be useful for users who

1. Want to auto-upgrade modules using `terraform init -u

Describe the issue
I wouldn't expect to get the alert if not defined explicitly.

Examples
https://github.com/hashicorp/terraform-provider-google/releases/tag/v4.0.0

Version (please complete the following information):

• Checkov Version 2.0.780

• 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

The --prod flag has been deprecated, so we should not show that field in the output of the env show command, or in our docs:

https://aws.github.io/copilot-cli/docs/concepts/environments/
https://aws.github.io/copilot-cli/docs/commands/env-show/

Description
When creating an aws_api_gateway_base_path_mapping via Terraform, driftctl believes that a aws_apigatewayv2_api_mapping resource is drifted, although none exists.

Environment
OS: Linux Ubuntu
driftctl version: v0.23.2
terraform version: v1.1.6
terraform providers versions: aws@v3.74.3

How to reproduce
If I create a aws_api_gateway_base_path_mapping via Ter