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

https://emotion.sh/

After this change in Material UI: mui-org/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"

Terraform resources can be created using for_each or count. This creates an array of resources. We could support setting usage values for all elements of the array by using a wildcard like this:

resource_usage:
  aws_cloudwatch_log_group.loggroup[*]:
    ...

I think expected functionality would be that the usage value should apply individually to each element of the array

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

Cloudprober supports building additional metrics (other than the default ones) from external probe output. We could possible do the same for HTTP probe.

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