We are very interested in a a usage file feature. Currently, the breakdown command supports specifying it as a parameter. It brings additional complexity to our CI pipeline, as we try to use the same Terraform code for different environments (dev/qa/prod). And obviously, different environments produce different usage.

So to make

What would you like to be added:
Currently there is the option to configure a --annotation-filter and a --source filter [0]. Since Kubernetes 1.19 the Ingress Resource was promoted to GA and got a new ingressClassName field.

I'd like to have a opti

https://emotion.sh/

After this change in Material UI: mui/material-ui#6115

The https://github.com/nccgroup/ScoutSuite/blob/master/ScoutSuite/providers/gcp/rules/findings/iam-lack-of-service-account-key-rotation.json finding should only flag USER_MANAGED keys (https://cloud.google.com/iam/docs/reference/rest/v1/projects.serviceAccounts.keys), as SYSTEM_MANAGED keys are "managed and rotated by Google"

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

Description

Currently there is no icon for DOCR:

Location

• Browser
• CLI
• API

Steps to reproduce

1. Provision a registry to DO or link one through the CLI
2. View connected docker registries from the "Integrations" tab

Additional Details

When we create a new table using an existing table config, it doesn't copy its children tables' configurations.

Join our new Discord Channel to say Hi and get live support from the team or from the community.

The functions in this file should be factored out to a separate utility lib as they are reused in bitcoin-etl https://github.com/blockchain-etl/ethereum-etl/blob/develop/ethereumetl/misc_utils.py