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

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

Description

Use Case

Ability to upgrade canaries to newest runtime ;-)

Proposed Solution

Add new constant here called SYNTHETICS_NODEJS_PUPPETEER_3_4 with value `new Runtime('syn-nodejs-puppeteer-3.4

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

Is your feature request related to a problem? Please describe.
I want to be able to disable a whole level of violation. For example the low error level i want to disable but still run the checks on medium, high, critical.

Describe the solution you'd like
I would like to have this possible with a simple flag in the ci to do this. To disable the violation level : low, etc. that when yo

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

Add GCE support for google_project_iam_custom_role (TF)

Sources

• Terraform Resource Documentation
• GCP Resource Documentation