-
Updated
Dec 20, 2020 - Rust
infrastructure
Here are 1,476 public repositories matching this topic...
-
Updated
Dec 16, 2020
-
Updated
Jan 19, 2021 - Ruby
Current behavior
All ShellTask logs are logged at DEBUG level, preventing showing the command output in the UI logs unless the agent's logging threshold is set to DEBUG. But this is undesired for production workloads, as this applies to all log messages
streaming logging for the ShellTask was introduced in #3584
Proposed behavior
change existing stream_logs parameter to `U
-
Updated
Dec 26, 2020
-
Updated
Jan 18, 2021 - Python
-
Updated
Jan 19, 2021 - Go
-
Updated
Dec 7, 2020
-
Updated
Jan 18, 2021 - C
-
Updated
Jan 18, 2021 - Python
-
Updated
Mar 27, 2020 - Ruby
-
Updated
Nov 22, 2018 - Go
-
Updated
Jan 18, 2021 - Java
-
Updated
Jan 19, 2021 - Ruby
-
Updated
Jan 4, 2021 - Go
-
Updated
Nov 14, 2019 - Go
-
Updated
Jan 18, 2021 - Python
-
Updated
Jan 19, 2021 - Python
-
Updated
Jan 12, 2021 - Python
-
Updated
Jan 18, 2021 - Python
-
Updated
Dec 29, 2020 - Ruby
-
Updated
Jan 8, 2021 - JavaScript
- 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
Jan 18, 2021 - Python
-
Updated
Jan 15, 2021 - HTML
-
Updated
Jan 5, 2021
-
Updated
Dec 11, 2020 - 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
When
backstage-cli lintis run in a package or plugin, it should take a look at the dependencies and throw warnings/errors based on some rules.