Description
The docs confused me a bit today: the Renderers page lists the gpg renderer as a text renderer. At the same time the salt.rendereres.gpg page uses it as a data renderer (last in the pipeline). This confused me for

I'm attempting to store some configuration variables in parameter store for my RDS cluster but am running into this validation error about instance size needing to be at least 1. It's comparing the token's value, which is a big negative number.

Reproduction Step

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

I updated the contributing docs to say the following. The aim of this ticket is to find all cost component names that change based on other params, and refactor them. There shouldn't be many, but finding them might take some grep foo, or VS Code might have a better answer...

The cost component name should not change when the IaC resource params change; anything that can change should be put in

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:
  docker.io/accurics/terrascan@sha256:cf459ae515849f2c004308c1a924958c3f92b121c94d64dcfac3849ce09b00b3

• Operating System:
  Docker

Description

When used in a pipeline, need to add full path otherwise it fails with an error. Would be logically if the Docker image's PATH environment variable had /go/bin in it.

What I Did

Images used:
    build 

I create a copilot job which defined COPILOT_APPLICATION_NAME as an environment variable. The infrastructure creation process failed with a rather obscure error message because that environment variable is injected automatically by copilot. Better validation of the manifest file would be more DX friendly.

acarlton@ubuntu:~/project$ aws-vault exec -n [account] -- copilot job deploy --name

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).