• 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]

Description

Simple UX in warnings

Today driftctl only displays which resource is concerned by the error, like:

WARN[0017] unable to parse line, invalid length, got 1 expected >= 2 line=github_repository.

It would be easier for the user if it read sth like:

WARN[0017] unable to parse line, invalid length, got 1 expected >= 2 line=63
Example

1. add an invalid line to

Add error handling during credentials onChange event so that the Scan Account feature does not activate if credentials are invalid

Because having to type the whole commands is a pain!

$ terratag -tags=var.default_tags
2020/09/24 23:09:46 Processing file cluster/ecs.tf
panic: invalid character 'v' looking for beginning of value

We should add the seguent targets to travis pipeline:

• Ubuntu 20.04
• Ubuntu 20.04 - image without netplan
• Ubuntu 18.04
• Ubuntu 18.04 - image without netplan

Also we could add (nice to have)

• Centos 7.x
• Debian 9

Description

When outputting results in the CLI, we could improve its readability by coloring certain aspects (e.g. Severity information, results output, etc.)