Separate variables for the mailer and database passwords
Demo / hello (push) Successful in 16s

gitea_mailer_password and gitea_postgresql_password each default to
gitea_admin_password, so the rendered values are unchanged until a
vault variable is set. Rotation steps are in
software-infrastructure docs/ci-cd/credentials.md.

Refs DevOps/software-infrastructure#47

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-13 18:18:52 -05:00
co-authored by Claude Opus 5.5
parent a4a75d8c8c
commit b5764c732a
2 changed files with 10 additions and 2 deletions
+8
View File
@@ -6,6 +6,14 @@
# 10.244.0.0/16 is the cluster pod network, where ingress-nginx runs.
gitea_trusted_proxies: "127.0.0.0/8,::1/128,10.244.0.0/16"
# Credentials, one per purpose. Each defaults to gitea_admin_password, which
# is how the role worked before they were separate, so applying the role with
# no new vault variables changes nothing. To give one its own value, define it
# in the vault and follow docs/ci-cd/credentials.md in software-infrastructure:
# some need a matching change outside the chart first.
gitea_mailer_password: "{{ gitea_admin_password }}"
gitea_postgresql_password: "{{ gitea_admin_password }}"
# Resources for chart subcharts. These match the limits previously set by
# hand on the live StatefulSets; the bitnami default presets (192Mi) OOM.
gitea_valkey_resources:
+2 -2
View File
@@ -134,7 +134,7 @@
SMTP_ADDR: postfix.eom.dev
SMTP_PORT: 587
USER: gitea
PASSWD: "{{ gitea_admin_password }}"
PASSWD: "{{ gitea_mailer_password }}"
FROM: Gitea <gitea@eom.dev>
ENVELOPE_FROM: gitea@eom.dev
ui:
@@ -166,7 +166,7 @@
postgresql:
auth:
username: gitea
password: "{{ gitea_admin_password }}"
password: "{{ gitea_postgresql_password }}"
database: gitea
primary:
resources: "{{ gitea_postgresql_resources }}"