[helm chart] add checksum annotations for schema and userProfile configmaps

[Gaspi]

No description provided.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ihiverlet]

@olevitt we are two in favor of checksum annotations now 😄

[ddecrulle]

Hello @Gaspi,

I agree that using a checksum is very convenient. However, the current PR introduces an implicit dependency on the file system.

I suggest defining the ConfigMap as a named template and including it both for rendering and for computing the checksum.
This makes the logic more robust and avoids relying on file path resolution.

{{- define "onyxia.XXXXX.configmap" }}
apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ template "onyxia.XXXXX.name" . }}
  labels:
    app: {{ template "onyxia.XXXXX.name" . }}
    chart: "{{ .Chart.Name }}-{{ .Chart.Version }}"
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
data:
  # ...
{{- end }}

# Include once to render the resource
{{- include "onyxia.XXXXX.configmap" . }}

Then in the Deployment:

annotations:
  checksum/config: {{ include "onyxia.XXXXX.configmap" . | sha256sum }}

Let me know what you think!