Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump org.sonatype.plugins:nexus-staging-maven-plugin from 1.6.13 to 1.7.0 #6

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
chore(deps): bump org.sonatype.plugins:nexus-staging-maven-plugin
Bumps org.sonatype.plugins:nexus-staging-maven-plugin from 1.6.13 to 1.7.0.

---
updated-dependencies:
- dependency-name: org.sonatype.plugins:nexus-staging-maven-plugin
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
dependabot[bot] authored Jun 25, 2024
commit f53ca3880f30dfbefa9962ba755725426b6a5066
2 changes: 1 addition & 1 deletion pom.xml
Original file line number Diff line number Diff line change
@@ -422,7 +422,7 @@
<plugin>
<groupId>org.sonatype.plugins</groupId>
<artifactId>nexus-staging-maven-plugin</artifactId>
<version>1.6.13</version>
<version>1.7.0</version>
<extensions>true</extensions>
<configuration>
<serverId>ossrh</serverId>

Unchanged files with check annotations Beta

# SPDX-License-Identifier: Apache-2.0
#
---
apiVersion: apps/v1

Check warning on line 23 in charts/item-relationship-service/templates/deployment.yaml

GitHub Actions / Analyze

[LOW] Pod or Container Without LimitRange

Each namespace should have a LimitRange policy associated to ensure that resource allocations of Pods, Containers and PersistentVolumeClaims do not exceed the defined boundaries

Check warning on line 23 in charts/item-relationship-service/templates/deployment.yaml

GitHub Actions / Analyze

[LOW] Pod or Container Without ResourceQuota

Each namespace should have a ResourceQuota policy associated to limit the total amount of resources Pods, Containers and PersistentVolumeClaims can consume
kind: Deployment

Check warning on line 24 in charts/item-relationship-service/templates/deployment.yaml

GitHub Actions / Analyze

[MEDIUM] Using Unrecommended Namespace

Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
metadata:
name: {{ include "irs.fullname" . }}
namespace: {{ .Values.namespace }}
matchLabels:
{{- include "irs.selectorLabels" . | nindent 6 }}
template:
metadata:

Check warning on line 40 in charts/item-relationship-service/templates/deployment.yaml

GitHub Actions / Analyze

[LOW] Missing AppArmor Profile

Containers should be configured with an AppArmor profile to enforce fine-grained access control over low-level system resources
annotations:
checksum/config: {{ include (print $.Template.BasePath "/configmap-spring-app-config.yaml") . | sha256sum }}
checksum/semanticmodels: {{ include (print $.Template.BasePath "/configmap-semantic-models.yaml") . | sha256sum }}
automountServiceAccountToken: false
securityContext:
{{- toYaml .Values.podSecurityContext | nindent 8 }}
containers:

Check warning on line 58 in charts/item-relationship-service/templates/deployment.yaml

GitHub Actions / Analyze

[LOW] Image Pull Policy Of The Container Is Not Set To Always

Image Pull Policy of the container must be defined and set to Always

Check warning on line 58 in charts/item-relationship-service/templates/deployment.yaml

GitHub Actions / Analyze

[LOW] Image Without Digest

Images should be specified together with their digests to ensure integrity
- name: {{ .Chart.Name }}
securityContext:
{{- toYaml .Values.securityContext | nindent 12 }}
- name: semantic-models
mountPath: /app/semantic-models
{{- end }}
env:

Check warning on line 73 in charts/item-relationship-service/templates/deployment.yaml

GitHub Actions / Analyze

[LOW] Secrets As Environment Variables

Container should not use secrets as environment variables

Check warning on line 73 in charts/item-relationship-service/templates/deployment.yaml

GitHub Actions / Analyze

[LOW] Secrets As Environment Variables

Container should not use secrets as environment variables
- name: MINIO_ACCESS_KEY
valueFrom:
secretKeyRef:
apiVersion: v1
kind: ConfigMap
metadata:
name: {{ include "irs.fullname" . }}-configmap

Check warning on line 26 in charts/item-relationship-service/templates/configmap-spring-app-config.yaml

GitHub Actions / Analyze

[MEDIUM] Using Unrecommended Namespace

Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
namespace: {{ .Values.namespace }}
data:
application.yaml: |-
---
apiVersion: v1
kind: Service
metadata:

Check warning on line 25 in charts/item-relationship-service/templates/service.yaml

GitHub Actions / Analyze

[MEDIUM] Using Unrecommended Namespace

Namespaces like 'default', 'kube-system' or 'kube-public' should not be used
name: {{ include "irs.fullname" . }}
namespace: {{ .Values.namespace }}
labels: