infrastructure

This issue is to collect a list of outstanding places where the Link component is imported not from @backstage/core-components but instead from other, generally 3rd party packages (e.g., MUI). The intent is to properly align the functionality of links across the system as a whole.

Links in the Backstage UI should be generated out of this component: https://backstage.io/storybook/?path=/stor

Description

It is not an actual bug but in the documentation here -> https://docs.prefect.io/orchestration/concepts/api.html#queries
flow_run actually needs to be flow_runs.
Otherwise it does not work for me.

Expected Behavior

Documentation should be updated.

Reproduction

Description

Add CLI bash completion of APIs and environments. Environments is lower priority.

Additional Context

• The operator will need an endpoint to provide the list of APIs. Which env to use? Pull it from the still-being-typed command (e.g. if --env aws is typed already)?
• Env names can be read from the CLI config
• [Cobra docs](https://github.com/spf13/cobra/blob/master

🚀 Feature Request

ENUMs for the catalyst-based conventions.
As an example, I will use scope.

Motivation

We have a lot of callbacks that used scope and maybe some other parameter that has only in catalyst-based meaning.
And every time we need to do something like that:

if isinstance(scope, str) and scope in [
            "on_batch_end",
            "on_batch_start",
  

• 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

A number of modules, and scripts in the test suite start with

#!/usr/bin/env python

In general it is better to use

#!/usr/bin/env python

because that allows execution inside a virtualenv, or when python is installed elsewhere, e.g. /usr/loca/bin/python.

There may be cases in which we really do want to hard code the path - for instance testing detection/selection of `

https://www.usenix.org/conference/opml19/program

Prepare to read papers

especially for less obvious but lengthy code snippets!