We have Changelog documentation here:

https://docs.saltproject.io/en/latest/topics/development/changelog.html

However, this documentation is not integrated or referenced in our documentation on how to create PRs:

https://docs.saltproject.io/en/latest/topics/development/contributing.html

The "Changelog" section appears BEFORE the Contributing section, but should likely be placed INSIDE

When trying to create a policy for CrossAccountDestination logs I've an error :
Error occurred while parsing policy: no statement block with AWS provider found. (Service: AWSLogs; Status Code: 400; Error Code: InvalidParameterException; Request ID: c4b2dad5-303d-4d9b-8461-d7be6c10d031; Proxy: null)

Reproduction Steps

The code :

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

See below ...

Monthly cost change for /home/atlantis/.atlantis/repos/XXX.tfplan
    Amount:  -$281 ($914 -> $633)
    Percent: --31%

Looks like a bug in this function: https://github.com/infracost/infracost/blob/master/internal/output/diff.go#L281

Hello,

Do you plan to support Terraform scans with OpenStack in the future ?

Regards

• 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]

Copilot doesn't seem to have correct error behavior when I try to create a Scheduled Job with the same name as an existing service.

For example, in my app right now I have the following:

❯ copilot svc ls
Name                Type
----                ----
fe                  Load Balanced Web Service

I can see this in SSM:

❯ aws ssm get-parameter --name /copilot/applicatio

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