• Missing information on how to create other databases
• Missing information on how to switch to other databases
• When using time travel, we don’t know where to get the transaction number from - we should show this to the user after committing data (this may be a missing capability in immudb / tools).
• The last long query example in the quick start is incorrect (incorrect

Saw this rule in the clj-kondo linter, and I think it would be a good addition to our strict mode. Having duplicate elements in sets is probably always a mistake in a production policy, and while it's "harmless", the intent is likely to provide another element rather than the duplicate, leading to an unexpected

Describe the issue

Check sources https://github.com/bridgecrewio/checkov/blob/master/checkov/cloudformation/checks/resource/aws/ALBListenerTLS12.py

Examples

  AppLB:
    Type: AWS::ElasticLoadBalancingV2::LoadBalancer
    Properties:
      Scheme: internet-facing
      Type: network                      # <<<<<<<<<<<<<<<<
      Subnets: !Ref Subnets
      LoadBalanc

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

Join our new Discord Channel to say Hi and get live support from the team or from the community.

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