Files
svcforge/deploy/chart/templates/externalsecret.yaml
T
Nguyen Minh Phuc 50c2fe2a1e
ci / lint (push) Successful in 1m19s
ci / unit (push) Failing after 1m2s
ci / integration (push) Has been skipped
ci / types (push) Successful in 1m37s
ci / security (push) Failing after 38s
ci / dockerfile (push) Successful in 14s
ci / image (api) (push) Has been skipped
ci / image (reconciler) (push) Has been skipped
ci / image (worker) (push) Has been skipped
ci / bump (push) Has been skipped
svcforge: reference implementation
Complete working build of the system learn-python/ teaches.
164 tests, mypy --strict clean, domain coverage 99%.
2026-07-17 10:44:54 +00:00

27 lines
995 B
YAML

{{- if .Values.externalSecret.enabled }}
{{/*
The Supabase and Upstash DSNs come from Vault via external-secrets. They are never chart
values, never CI variables, and never baked into an image layer — the chart names the
Vault path, and the cluster resolves it.
The rendered Secret is consumed with envFrom, so adding a key here is the only step needed
to expose a new one; settings.py (env_prefix="SVCFORGE_") types it on the way in and fails
fast if it is missing or malformed.
*/}}
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: {{ include "svcforge.fullname" . }}-secrets
labels:
{{- include "svcforge.labels" . | nindent 4 }}
spec:
refreshInterval: {{ .Values.externalSecret.refreshInterval }}
secretStoreRef:
{{- toYaml .Values.externalSecret.secretStoreRef | nindent 4 }}
target:
name: {{ include "svcforge.secretName" . }}
creationPolicy: Owner
data:
{{- toYaml .Values.externalSecret.remoteRefs | nindent 4 }}
{{- end }}