Skip to content

Commit 0062ae4

Browse files
waleedlatif1claude
andcommitted
fix: use a renderable placeholder for externalDatabase.password
The chart validates the password against ^[a-zA-Z0-9._-]+$, so the `<password>` placeholder I added last round made the reference topology fail to render if copied as-is. Replaced with a compliant placeholder and documented the character restriction, which is a real constraint operators hit when generating one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015BwsJTEQRzWJaY4BRCkPZt
1 parent 82d884f commit 0062ae4

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

  • apps/docs/content/docs/platform/self-hosting

apps/docs/content/docs/platform/self-hosting/scaling.mdx

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -147,11 +147,15 @@ externalDatabase:
147147
port: 6432
148148
database: simstudio
149149
sslMode: require
150+
# Replace with your real password. It must match ^[a-zA-Z0-9._-]+$ — the
151+
# chart rejects anything else, including the angle brackets a placeholder
152+
# would normally use.
153+
#
150154
# Required unless you use externalDatabase.existingSecret or External
151-
# Secrets, either of which skips this check. Under External Secrets, map
155+
# Secrets, either of which skips both checks. Under External Secrets, map
152156
# externalSecrets.remoteRefs.externalDatabase.password — an omitted mapping
153157
# renders no Secret and the pod cannot start.
154-
password: "<password>"
158+
password: "replace-with-your-password"
155159
156160
autoscaling:
157161
enabled: true

0 commit comments

Comments
 (0)