infrastructure-as-code

Describe the solution you'd like
It would be nice to have a way to control whether a VM starts on boot or not. Maybe a new autostart option to salt.states.virt.running and/or salt.states.virt.defined? Or maybe a new function?

Describe alternatives you've considered
I'll probably use salt.modules.virt.set_autostart for now.

AlmaLinux should be detected as RHEL/CentOS. Trivy should be able to detect RHEL/CentOS vulnerabilities

https://almalinux.org/

cron expressions are now allowed on synthetic canaries. Similar to app-autoscaling and autoscaling and other modules, the synthetic Schedule class should support a static cron method that takes in cronOptions.

I think w

It does not look like we can detect "Fast snapshot restore" from the Terraform resource. Reading the AWS pricing page > "EBS Fast Snapshot Restore" example, I think we should hide that cost component by default and instead add a "fast_snapshot_restore_hours: 2 # Number

Is your feature request related to a problem? Please describe.
Yes. We've inherited a terraform repo with a lot of legacy problems. We've introduced checkov to ensure new config going
forward meets our standards. We've also generated baseline files for all of the existing legacy terraform config, so that we only fail checks for new problems. However, we'd like to keep visibility on all

• 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

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