infrastructure

Would be good to upgrade the commander dependency in @backstage/cli.

Dependabot tried, but it looks like there's some breaking API changes.

backstage/backstage#10192

Opening up to the community to do as a good first issue! 👍

Description

Occasionally I get the following error when running sub-flows using create_flow_run and wait_for_flow_run

Task "wait_for_flow": Exception encountered during task execution!
Traceback (most recent call last):
  File "/root/miniconda3/lib/python3.8/site-packages/prefect/engine/task_runner.py", line 876, in get_task_run_state
    value = prefect.utilities.executor

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

• 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/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, e.g.

• testing detection/selection of `ansible_py

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

Prepare to read papers

especially for less obvious but lengthy code snippets!