Description
On this page: https://docs.saltproject.io/en/master/topics/development/contributing.html#pr-time
The link in the text in the first sentence "PR Guidelines" is linking to the develop branch and thus hitting a 404 page and should be going to https://docs.saltproject.io/en/master/topics/development/pull_requests.html or latest

Expected behavior
Expected to hit latest or mast

JobDefinition.buildJobContainer() explicitly only renders devices from container.linuxParams, omitting all other parameters.

The implementation for JobDefinition makes it seem like this is intentional.

Reproduction Steps

new JobDefinition(this, 'jobDef', {
    container: {
        linuxParams: new LinuxParameters(this, 'linuxParams', {
          sharedMemory

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

The following resource returns no prices, but according to this the EU multi-region has prices:

  NAME                                                       MONTHLY QTY  UNIT            PRICE   HOURLY COST  MONTHLY COST

  google_storage_bucket.my_storage_bucket
  ├─ Storage (standard)                                                -  GiB-months

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

• terrascan version: 1.2
• Operating System: all

Description

When scanning a repo, if the severity field is not all caps (HIGH|MEDIUM|LOW), when violations are output, the color of the severity field does not show up. The compare should be case-insensitive, OR we can normalize the severity field.

What I Did

terrascan scan -d [dir]

I typoed my AWS_PROFILE name, so copilot init died, but it wasn't immediately obvious from the below output.

My suggestion is less of the debugging verbiage (unless the user requests it with --debug / --verbose) and more human friendly guidance like, "No valid AWS credentials found. Please read this doc <link to AWS credentials docs> to learn how to configure credentials."

$

Garbage collection works by listing everything with the gc-tag. In a busy cluster, we really want that filter to happen server-side and ideally using an index of some sort.

That means we should use a Kubernetes label, not an annotation.

I think this will require a two-step migration plan (write both but continue to read annotation; release; drop support for annotation; release).