As a result of the showcase, we should improve the following messages:

• “column does not exist”: Which one?
• “syntax error: unexpected IDENTIFIER”: Would like to
• have a hint where to look for the error in my statement.
• "pq: syntax error: unexpected $unk"

Short description

We are using opa's discovery feature to dynamically download s3 bundles. Our policy file looks as shown below. This policy successfully downloads and activates "/main_bundle/authz.tar.gz".

package discovery

bundle_config := {
  "bundles": {
    "main": {
      "service": "s3_service",
      "resource": bundle_name
    },
  },
  "default_decision": "/aut

Describe the issue
It seems like Checkov Terraform scan introduces false positive checks when assigning aws_security_group to aws_memorydb_cluster resource

Examples
The following resources were defined in the same .tf file without using modules.

resource "aws_security_group" "secgrp" {
  ...
  name        = "test-redis-secgrp"
  description = "test-redis-secgrp"
  

The command exist test always returns true regardless of if the command is invalid.

Describe the problem

On Windows, we want to test if a command/cmdlet exists before running it. However, the 'command().exist?‘ test always returns true no matter what command t

Some of our log messages start with a capital letter and some don't.
We should ensure the messages are consistent and use a single style.

See example to inconsistency in cloudquery/cloudquery#1059:

Extend macro function that creates OCIL entries for package removed rules to support both package removed/installed rules using an extra parameter to define the behavior of the ocil_clause (the ocil clause "package is installed" for removed package rules and "package is not installed" for installed package rules)

https://github.com/ComplianceAsCode/content/blob/fe68fcd788b85eed7559e6174d71a67

We should make it easier to install this plugin.

Good summary at https://matthewdf10.medium.com/how-to-enable-logging-on-every-aws-service-in-existence-circa-2021-5b9105b87c9 and https://docs.google.com/spreadsheets/d/1DBmCXX1irJvxdewa85p5nSsYEf3tpSKWBbwp700mbzs/edit#gid=0

Amazon Aurora
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-rds-dbcluster.html#cfn-rds-dbcluster-enablecloudwatchlogsexports

AWS AppSync

Describe the bug
When using parse-tree command, error information in printed twice with slightly different text.

To Reproduce
Please supply:

var status = ['ACTIVE']

NOTE: Please be sure that the templates, rules and logs you provide as part of your bug report do not contain any sensitive information.

Expected behavior
There should be one error log instead of dupli

The code at

https://github.com/oss-review-toolkit/ort/blob/fd1b62a799523b55871cd04001ddfe1e6262da0f/analyzer/src/main/kotlin/managers/Stack.kt#L113-L140

can be simplified now that Stack 2.3.1 supports ls dependencies json.

I think the lines in the following documentation are somehow not in correct order. Maybe chunks were added between multi line statements. Especially import_str: is broken.

https://github.com/tern-tools/tern/blob/a3e76cdb0e08d92e896822634cbcf670bdd05e30/tern/classes/image_layer.py#L18-L43

Description

The /info API returns the fossslogy version as unknown when the sever is running from docker.

![image](https://user-images.githubusercontent.com/63705023/161546