Skip to content
#

infrastructure

Here are 1,481 public repositories matching this topic...

backstage
dcalde
dcalde commented Dec 17, 2020

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

Saves up to 90% of AWS EC2 costs by automating the use of spot instances on existing AutoScaling groups. Installs in minutes using CloudFormation or Terraform. Convenient to deploy at scale using StackSets. Uses tagging to avoid launch configuration changes. Automated spot termination handling. Reliable fallback to on-demand instances.

  • Updated Jan 4, 2021
  • Go
terrascan
williepaul
williepaul commented Jan 15, 2021
  • 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]

Improve this page

Add a description, image, and links to the infrastructure topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the infrastructure topic, visit your repo's landing page and select "manage topics."

Learn more