-
Updated
Feb 14, 2022 - Shell
compliance
Here are 404 public repositories matching this topic...
Quickstart review
- 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
Every now and then we see users new to OPA missing the fact that /v1/data requires the JSON request body to wrap the input document, ala: {"input": {"x": "y"}}. Unless e.g. default assignment is used, OPA currently returns just an empty response for a request missing the "input" wrapper, i.e. {"x": "y"} ... it's easy to see why this would be, given how people likely have worked on their po
-
Updated
Mar 4, 2022 - Shell
Is your feature request related to a problem? Please describe.
I want to be able to disable a whole level of violation. For example the low error level i want to disable but still run the checks on medium, high, critical.
Describe the solution you'd like
I would like to have this possible with a simple flag in the ci to do this. To disable the violation level : low, etc. that when yo
-
Updated
Mar 4, 2022 - Python
Describe the issue
I wouldn't expect to get the alert if not defined explicitly.
Examples
https://github.com/hashicorp/terraform-provider-google/releases/tag/v4.0.0
Version (please complete the following information):
- Checkov Version 2.0.780
-
Updated
Jan 17, 2022 - C
-
Updated
Mar 4, 2022 - 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.
-
Updated
Mar 4, 2022 - Shell
-
Updated
Sep 12, 2018 - HTML
`make install`
We should make it easier to install this plugin.
-
Updated
Mar 1, 2022 - Python
-
Updated
Feb 28, 2022 - Go
-
Updated
Feb 15, 2022 - 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
Mar 4, 2022 - CSS
-
Updated
Dec 27, 2021 - Go
The code at
can be simplified now that Stack 2.3.1 supports ls dependencies json.
-
Updated
Mar 3, 2022 - 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.
When using an SPDX LicenseRef license these will normally not be recognized by Nomos., as a result Nomos will report it as License Not Found, which the decider sees and refuses to conclude that license.
If the license is one that the team has used before and is on the main list of licenses then it should be possible to automatically conclude that license so long as other matchers do not disagr
-
Updated
Feb 23, 2022 - Go
-
Updated
Jan 4, 2022 - Ruby
Hi,
Are there any plans to support junitxml output support? This would make it easier to integrate into CI/CD pipelines with reports and metrics.
Thanks
-
Updated
Mar 3, 2022 - Scala
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."