-
Updated
Jan 31, 2021 - Rust
infrastructure
Here are 1,498 public repositories matching this topic...
-
Updated
Feb 13, 2021
-
Updated
Feb 17, 2021 - Ruby
Description
I have setup a custom, remote prefect server.
However, when registering a flow, only localhost is displayed in the Flow URL :
$ prefect register flow --file ./myflow.py -p sandbox
Result check: OK
Flow URL: http://localhost:8080/default/flow/9235a237-f6bc-41c7-89bc-132db233b49e
└── ID: a09a47b0-1292-412f-bd70-89c8bf4dcf1e
-
Updated
Dec 26, 2020
-
Updated
Jan 18, 2021 - Python
-
Updated
Feb 16, 2021 - Go
-
Updated
Dec 7, 2020
-
Updated
Feb 12, 2021 - C
-
Updated
Feb 15, 2021 - Python
-
Updated
Mar 27, 2020 - Ruby
-
Updated
Nov 22, 2018 - Go
-
Updated
Feb 16, 2021 - Java
-
Updated
Feb 16, 2021 - Ruby
-
Updated
Jan 26, 2021 - Go
-
Updated
Nov 14, 2019 - Go
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 `
-
Updated
Feb 16, 2021 - Python
- terrascan version: 1.2
- Operating System: all
Description
When scanning a repo, if the severity field is not all caps (HIGH|MEDIUM|LOW), when violations are output, the color of the severity field does not show up. The compare should be case-insensitive, OR we can normalize the severity field.
What I Did
terrascan scan -d [dir]
-
Updated
Feb 10, 2021 - Python
-
Updated
Feb 15, 2021 - Python
-
Updated
Feb 17, 2021 - Ruby
-
Updated
Jan 8, 2021 - JavaScript
-
Updated
Feb 8, 2021 - Python
-
Updated
Feb 15, 2021 - HTML
-
Updated
Feb 15, 2021
-
Updated
Jan 31, 2021 - Rust
Improve this page
Add a description, image, and links to the infrastructure topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the infrastructure topic, visit your repo's landing page and select "manage topics."


Feature Suggestion
I need a way to get the organization engaged with our new Backstage portal. It needs to become a place that everyone goes for information. It needs to be always at the developer's fingertips. Switching between GitHub and Backstage should feel natural and seamless. Navigation has to be bi-direc