infrastructure-as-code

Our documentation says that cidrnetmask() only works with IPv4. But a user tried using it with can(cidrnetmask()) and found out that it doesn't actually error with IPv6. For either IPv4 or IPv6, it returns a netmask.

It is technically invalid to create a netmask for IPv6, so we should correct the behavior of this function to retur

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

Container scanning schemas below 14.0.0 have been deprecated.

blob/main/contrib/gitlab.tpl:3 is using a deprecated version:

"version": "2.3",

The latest version of the schema is [14.1.0](https://gitlab.com/gitlab-org/gitla

What is the problem?

This MR added the ability to enable control plane logging for eks clusters. This doesn't work for a fargate cluster because the ClusterProps interface is not included in FargateCluster.

Can I make an MR where I move ClusterLogging to ClusterOptions? Also open to other solutions of course.
I thought I would ask and wait fo

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

Currently, if I want to check for the logs of exited tasks, I need to go to AWS console, navigate to ECS, find the cluster, then the service, than switch to stopped tasks, then search for the logs there.

It would be helpful to have a copilot svg logs -p where -p stands for "previous task" (like k8s), that dumps the logs of the most recent stopped task.

Besides that, an `copilot svc logs

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