infrastructure

Expected Behavior

Actual Behavior

Steps t

Hello!

I've found an issue here:[Bitbucket Storage](https://docs.prefect.io/api/latest/storage.html#github) is a storage option that uploads flows to a Bitbucket repository as .py files.

Page reference: https://docs.prefect.io/orchestration/flow_config/storage.html#bitbucket

First, the link is incorrect. Second, should the line read more like Github where it references the repository

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

What is the problem this feature would solve? Please describe.

Currently there aren't any examples showing what a path should look like. Does it start with a leading slash? Do you need the bucket name like you do in s3cmd? Can you start with a wildcard to flush everything with a given file extension?

The fact that doctl always returns an empty success makes it even more difficult to dete

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!