See infracost/infracost#1135 and the follow-up comment for what's needed

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"

Hello Team,
Here is the my current checkov_scan.yml file
name: Run Checkov action serverless
id: checkov1
uses: bridgecrewio/checkov-action@master
with:
#skip_check: CKV_AWS_23 # optional: skip a specific check_id
#quiet: true # optional: display only failed checks
#log_level: DEBUG # optional: set log level. Default WARNING

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

Is your feature request related to a problem? Please describe.

We don't want giving our staff ADMIN permissions, but they need to be able to add new option values without distracting us every time.

Describe the solution you'd like

Everyone authenticated should be able to manage option values. This can be also configured on a field level (e.g. "Who can manage option values: Everyon

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