Avoid proxy rollouts on chart metadata changes

Summary:

Hash only the rendered HAProxy configuration for the pod-template checksum instead of the entire ConfigMap manifest. This prevents chart label and other metadata-only changes from triggering a Deployment rollout.

Test Plan:

- `helm lint charts/whatsapp-proxy-chart --values /data/users/bsuh/configerator/raw_configs/cloud/helm/values/wa_unblock/whatsapp-proxy-chart/common_values.yaml --values /data/users/bsuh/configerator/raw_configs/cloud/helm/values/wa_unblock/whatsapp-proxy-chart/chat_values.yaml`
- Rendered the chart with `helm template` and verified the checksum is a valid SHA-256 value.
- Changed the chart version to `9.9.9` in a temporary chart copy and verified the rendered HAProxy checksum remained unchanged.

Reviewers:

Subscribers:

Tasks:

Tags:

Author: bsuh

charts/whatsapp-proxy-chart/templates/deployment.yaml

@@ -18,7 +18,7 @@ spec:
   template:
     metadata:
       annotations:
-        checksum/haproxy-config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }}
+        checksum/haproxy-config: {{ tpl .Values.haproxyConfig . | sha256sum }}
         {{- with .Values.podAnnotations }}
         {{- toYaml . | nindent 8 }}
         {{- end }}