Update to DTR Client Lib, BOM lifecycle asSpecified #578
Annotations
1 error and 10 warnings
|
|
|
irs-api/src/main/resources/application-local.yml#L9
Query to find passwords and secrets in infrastructure code.
|
|
irs-api/src/main/resources/application-local.yml#L3
Query to find passwords and secrets in infrastructure code.
|
|
charts/irs-helm/values.yaml#L227
Query to find passwords and secrets in infrastructure code.
|
|
charts/irs-helm/templates/service.yaml#L1
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
charts/irs-helm/templates/deployment.yaml#L1
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
charts/irs-helm/templates/configmap-spring-app-config.yaml#L1
Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
|
|
charts/irs-helm/templates/deployment.yaml#L1
Containers must have the same resource requests set as limits. This is recommended to avoid resource DDoS of the node during spikes and means that 'requests.memory' and 'requests.cpu' must equal 'limits.memory' and 'limits.cpu', respectively
|
|
.config/spectral/restBasicSecurity.yml#L1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions
|
|
.github/workflows/helm-test-backwards-compatability.yaml#L1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions
|
|
.github/dependabot.yml#L1
IAM Access Analyzer should be enabled and configured to continuously monitor resource permissions
|
The logs for this run have expired and are no longer available.
Loading