Minor annoyance department, but still.

Expected Behavior

Switching between version in the docs should jump between versions of the page currently viewed.

Actual Behavior

Changing version always take you to the introduction page.

Describe the problem

when executing an inspec profile from a remote repository with a default branch not named master the following error is returned.

inspec exec https://github.com/org/profile.git

Profile git dependency failed - unable to resolve ma

Describe the bug
CKV_GCP_14 requires a backup configuration, but it does not take into consideration read replicas.
A read replica cannot have backup enabled in GCP.

To Reproduce
Steps to reproduce the behavior:

1. Create a google_sql_database_instance with master_instance_name and replica_configuration
2. Chekov will pop up error CKV_GCP_14

Expected behavior
Read replicas

Description

These files need some review as there are some weird licenses detected:

• https://raw.githubusercontent.com/twbs/bootstrap/v3.3.6/docs/dist/css/bootstrap.min.css.map
• https://raw.githubusercontent.com/twbs/bootstrap/v3.3.6/dist/css/bootstrap-theme.min.css.map
• https://raw.githubusercontent.com/eclipse/org.aspectj/V1_8_7/weaver/src/aspectj_1_5_0.dtd
• https://raw.githubuserco

We should make it easier to install this plugin.

Describe the bug

Different error messages are being returned by resource type and log type validations depending on validations occuring in the bulk_upload handler vs the individual resource create handlers.

Analysis Items have validation checks for resource and logtypes depending on the analysis item type (Added in PR 2548

Items c

Description

When i reuse a component, the agent log is getting printed which is not required.

How to reproduce

• Upload component x-01,
• Do some clearing.
• Upload component x-1.5 by reusing the x-01.
• Go to show jobs view and click on job-id of reuse.

Screenshots

<img width="555" alt="screenShot10" src="https://user-images.githubusercontent.com/10155976/10672

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.

Description

Currently add_failure takes the values required to create a failure, creates it then adds it to the Result object's failed_rules
On the other hand add_warning takes a Failure object directly.

Proposed solution

The methods should be updated so that they both have the same behavior (or maybe even just add an add_finding method which takes a type that can be either Failure o