Dionysius
Dionysius
#### Description of Problem: Today with containerisation of systems and/or applications there's very low memory available for running oscap. Hello cgroups, docker, lxc, lxd, incus, kubernetes, etc. Most OVAL definitions...
## Describe the Bug I've written a catch_error with followup type check to =~ Error exactly like written in the bolt docs ["catching errors in plans"](https://www.puppet.com/docs/bolt/latest/writing_plans.html#catching-errors-in-plans). If I use the...
#### What happened: Followup for https://github.com/kubernetes-sigs/cri-tools/issues/1244. It is time to reflect the correct repo/link in the Readme in some way. #### What you expected to happen: The Readme doesn't send...
As described in #586 > The Nexus Repo generated Packages file does not follow the DebianRepository spec in regard to the Filename: field. > > The Filename: field that Nexus...
Error message: > * Ingress.networking.k8s.io "apisix-control" is invalid: spec.rules[0].http.paths[0].backend: Required value: port name or number is required There is an inconsistency between the values.yaml and the chart template. - chart...
- etcd credentials: https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix-dashboard/templates/configmap.yaml#L38-L43 - dashboard users: https://github.com/apache/apisix-helm-chart/blob/master/charts/apisix-dashboard/templates/configmap.yaml#L62-L66