-
Updated
Nov 9, 2021 - Shell
compliance
Here are 369 public repositories matching this topic...
-
Updated
Nov 12, 2021 - Shell
-
Updated
Nov 11, 2021 - Python
-
Updated
Oct 15, 2021 - C
-
Updated
Nov 12, 2021 - Go
Hello Team,
Here is the my current checkov_scan.yml file
name: Run Checkov action serverless
id: checkov1
uses: bridgecrewio/checkov-action@master
with:
#skip_check: CKV_AWS_23 # optional: skip a specific check_id
#quiet: true # optional: display only failed checks
#log_level: DEBUG # optional: set log level. Default WARNING
AFTER TX support
Other than BEFORE TX we could expose AFTER TX as a SQL method
-
Updated
Nov 12, 2021 - C
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
Say Hi on Discord!
Join our new Discord Channel to say Hi and get live support from the team or from the community.
Description of problem:
The bash remediation of selinux_state runs:
fixfiles onboot
fixfiles -f relabel
whereas the Ansible remediation doe
-
Updated
Sep 12, 2018 - HTML
`make install`
We should make it easier to install this plugin.
-
Updated
Nov 9, 2021 - Python
-
Updated
Nov 8, 2021 - Go
-
Updated
Apr 6, 2021 - Go
-
Updated
Nov 11, 2021 - XSLT
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
-
Updated
Nov 5, 2021 - Go
-
Updated
Sep 21, 2021 - JavaScript
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.
Private github repos
It might be helpful to inform people in the guide some hints on setting up private repos such as github using the docker container.
git config --global url."https://$GITHUB_USERNAME:$GITHUB_PASSWORD@github.com".insteadOf /"https://github.com"
ls -l ~/.gitconfigdocker run -e -v $(pwd):/project \
-v ~/.gitconfig:/root/.gitconfig \
ort:latest --info anDescription
While testing PR #1955, found following thing.
For an upload, there are only 2 failed jobs (readmeoss and ojo) but the REST API says "status": "Failed" for every single job even when all child job has "status": "Completed".
Maybe the "status" of a job can be limited only to its child jobs' statuses.
Screenshots
![image](https://user-images.githubusercontent.
-
Updated
Nov 1, 2021 - Ruby
-
Updated
Oct 4, 2021 - Go
-
Updated
Nov 11, 2021 - Scala
-
Updated
Sep 30, 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."
These two examples point to hardcoded playground URLs, https://play.openpolicyagent.org/p/ikesWCFIH8 and https://play.openpolicyagent.org/p/oL4Ofd1nQi.
They contain input documents that don't match the latest kubernetes schema, i.e.
"apiVersion": "admission.k8s.io/v1beta1".The