-
Updated
Jan 22, 2021 - Shell
compliance
Here are 310 public repositories matching this topic...
-
Updated
Feb 10, 2021 - Python
-
Updated
Jan 6, 2021 - C
-
Updated
Feb 9, 2021 - Shell
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
GEN003 is triggering for the name of a secret in a github_actions_organization_secret resource. Going off the documentation for GEN003, it should only be triggering for secret VALUES, and not secret NAMES.
To Reproduce
variable "value"-
Updated
Feb 11, 2021 - C
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:
- Create a google_sql_database_instance with master_instance_name and replica_configuration
- Chekov will pop up error CKV_GCP_14
Expected behavior
Read replicas
-
Updated
Feb 10, 2021 - Go
-
Updated
Sep 12, 2018 - HTML
-
Updated
Feb 10, 2021 - Python
-
Updated
Feb 10, 2021 - Go
There are several files we could squeeze data from:
- packages.config https://docs.microsoft.com/en-us/nuget/reference/packages-config
- https://docs.microsoft.com/en-us/nuget/consume-packages/migrate-packages-config-to-package-reference
- https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-properties
- https://docs.microsoft.com/en-us/visualstudio/msbuild/customize-your-build
- vbp
`make install`
We should make it easier to install this plugin.
-
Updated
Feb 8, 2021 - Python
Overview:
Developers may run mage commands against multiple different versions of panther.
The mage logs do not specify the version of panther.
If we have the git commit we can be sure of the command context.
Example:
Specifically I am running integration tests for release testing. I pulled the repo and achieved successful integration test results. Pull resulted in updates to
-
Updated
Feb 9, 2021 - XSLT
-
Updated
Feb 3, 2021 - JavaScript
-
Updated
Jan 22, 2021 - Go
-
Updated
Jan 24, 2021 - Ruby
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
can be simplified now that Stack 2.3.1 supports ls dependencies json.
-
Updated
Feb 9, 2021 - Scala
-
Updated
Feb 9, 2021 - Python
-
Updated
Jul 30, 2020
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
-
Updated
Jul 28, 2020
-
Updated
Feb 8, 2021 - Python
Improve this page
Add a description, image, and links to the compliance topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the compliance topic, visit your repo's landing page and select "manage topics."
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.