use a feature flag for care partner alerts mongo connectors

As they're not in use right now, they tend to fall off of the op log and cause needless alerts. BACK-3365
tidepool-org · Jan 16, 2025 · f1c866a · f1c866a
1 parent ac0c6b1
commit f1c866a
Show file tree

Hide file tree

Showing 3 changed files with 7 additions and 0 deletions.
diff --git a/charts/tidepool/charts/data/templates/8-care-partner-alerts-kafka-connector.yaml b/charts/tidepool/charts/data/templates/8-care-partner-alerts-kafka-connector.yaml
@@ -1,4 +1,5 @@
 {{ if .Values.global.kafka.connect.enabled }}
+{{ if .Values.kafka.connectors.carePartnerAlerts.enabled }}
 apiVersion: kafka.strimzi.io/v1beta2
 kind: KafkaConnector
 metadata:
@@ -24,3 +25,4 @@ spec:
     heartbeat.topic.name: {{ .Release.Namespace }}-{{ .Values.global.kafka.connect.clusterName }}-heartbeat
   tasksMax: {{ .Values.global.kafka.connect.sourceTasksMax | int }}
 {{- end }}
+{{- end }}
diff --git a/charts/tidepool/charts/data/templates/8-device-data-kafka-connector.yaml b/charts/tidepool/charts/data/templates/8-device-data-kafka-connector.yaml
@@ -1,4 +1,5 @@
 {{ if .Values.global.kafka.connect.enabled }}
+{{ if .Values.kafka.connectors.carePartnerAlerts.enabled }}
 apiVersion: kafka.strimzi.io/v1beta2
 kind: KafkaConnector
 metadata:
@@ -34,3 +35,4 @@ spec:
     heartbeat.topic.name: {{ .Release.Namespace }}-{{ .Values.global.kafka.connect.clusterName }}-heartbeat
   tasksMax: {{ .Values.global.kafka.connect.sourceTasksMax | int }}
 {{- end }}
+{{- end }}
diff --git a/charts/tidepool/charts/data/values.yaml b/charts/tidepool/charts/data/values.yaml
@@ -34,6 +34,9 @@ kafka:
   configmapName: kafka
   # -- name of the configmap containing the kafka broker and credentials to use
   secretName: kafka
+  connectors:
+    carePartnerAlerts:
+      enabled: false
 # -- node selector configuration
 nodeSelector: {}
 # -- tolerations