policy
Here are 447 public repositories matching this topic...
Is your feature request related to a problem? Please describe.
We have a file pkg/policy/defaultRules.yaml - which is the source of truth for the default rules in users' policies.
It's very important we don't break it, therefore - better testing is required.
A quick win would be to test and validate the structure of the yaml
Describe the solution you'd like
Add a test file **pkg/pol
-
Updated
Feb 16, 2022 - Sass
-
Updated
Feb 15, 2021
-
Updated
Apr 7, 2022 - C
-
Updated
Jul 11, 2021 - HTML
-
Updated
Mar 3, 2022 - AGS Script
-
Updated
Apr 1, 2022
-
Updated
Feb 8, 2022
-
Updated
Dec 25, 2020 - Python
Use duct.rs in xtask
https://github.com/oconnor663/duct.rs
It looks like it may simplify slightly some of the logic related to creating commands and spawning tasks in the background.
-
Updated
Apr 7, 2022 - Python
-
Updated
Apr 7, 2022
-
Updated
Apr 7, 2022 - Java
-
Updated
Apr 4, 2022 - Go
-
Updated
Feb 28, 2022 - Go
-
Updated
Apr 6, 2022 - Open Policy Agent
-
Updated
Apr 7, 2022 - C++
Feature Request
Short Description
Currently, the GRPC server port [is a configuration](https://github.com/kubearmor/KubeArmor/blob/bf39613c0c01e986d3e77d2f46a59c526cbf5907/KubeArmor/config/config.go#L79) and the default value is 32767.
This works fine on kubearmor in
-
Updated
Aug 27, 2018 - HTML
When the server rebuilds the policy index and detects any errors, it only outputs a summary of the errors detected (failed to build index: missing imports=1, duplicate definitions=0, load failures=2). This is for two reasons:
- We expect users to always run
cerbos compileto catch any problems before pushing any policy changes live. - If there are too many errors, reporting them all in th
-
Updated
Apr 6, 2022 - Go
-
Updated
Apr 5, 2022 - Go
-
Updated
Jun 13, 2020 - Go
-
Updated
Apr 7, 2022 - HTML
-
Updated
Feb 4, 2022 - Python
Improve this page
Add a description, image, and links to the policy topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the policy topic, visit your repo's landing page and select "manage topics."
Currently, whenever there's a patch release, like
0.36.1, that becomes the only displayed docs version in the version picker:That's fine. However, we also stop generating website content for the previous versions, so 0.36.0 disappears: https://www.openpolicyagent.org/docs/v0.36.