rittneje
rittneje
If we prepare a request normally (the `prepare()` method), it does not include any additional headers by default, even if the resulting prepared request is sent via a session. However,...
Since `acutest_check_` specifically expects an `int` for the condition, we cannot currently do a truthiness check with `TEST_CHECK`/`TEST_ASSERT` without a compiler warning. For example, the following will emit a warning:...
When using `TEST_ASSERT` and `TEST_ASSERT_`, it seems the program exits before stdout and stderr are flushed, meaning the corresponding messages don't show up in the output. Please add the following...
Currently the GitHub releases include two assets (among others): cert-manager.crds.yaml and cert-manager.yaml. The former only includes the CRD specs, while the latter is everything (CRDs, deployments, service accounts, etc.). I...
https://github.com/kubernetes-sigs/aws-iam-authenticator/blob/e61f537662b64092ed83cb76e600e023f627f628/pkg/token/token.go#L507-L509 The error from `http.NewRequest` is not being checked, so it is possible for `req` to be `nil`.
### Name of the resource AWS::EKS::Cluster ### Resource Name _No response_ ### Issue Description EKS supports enabling (but not disabling) secret encryption on an existing cluster. https://docs.aws.amazon.com/eks/latest/userguide/enable-kms.html However, attempting to...
At present the documentation for [`keep-alive`](https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#keep-alive) is rather vague as to its type or unit. > Sets the time during which a keep-alive client connection will stay open on the...
v1.3.0 introduced the `EnableRandPool` and `DisableRandPool` functions as a means of optimizing UUID generation at the expense of security. However, there are two main issues with this. First, as documented,...
This tool does not handle wildcards in IAM policy actions properly, because it only does literal string matches. For example, the `PrivilegeEscalation` class will not detect any issue if my...
I am reopening #3884 because it should not have been closed. The workaround presented by @jasdel does not address the stated problem. **Is your feature request related to a problem?...