https://emotion.sh/

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

Running infracost breakdown --config-file infracost.yml --terraform-workspace=ali-test correctly shows:

Error: --config-file flag cannot be used with the following flags: --path, --terraform-*, --usage-file

Our help text mentions the same thing:
      --config-file string            Path to Infracost config file. Cannot be used with path, terraform* or usage-file flags

However,

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"

Uploading the SARIF formatted output to the GH repo fails. It does not appear to be valid SARIF according to the parser. Using the github/codeql-action/upload-sarif@v1 produces an error message with invalid data.

To Reproduce
Steps to reproduce the behavior:

1. Create a GH Action with the following steps to run the checkov scan and generate a checkov.sarif results file:

- name

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

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

Feature Request
Send message in a Discord Channel

Additional context

• To get started, read how extensions work in this wiki.
• Template for extensions
• Extension should to be added via PR to the [extensions library]( https://githu

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