Replies: 1 comment
-
|
try smtg like: postgresServer: defect-dojo-rw.defect-dojo-db.svc.cluster.local # your hostname; note this is a top-level value
postgresql:
enabled: false
auth:
username: defect-dojo # your database user
database: defect-dojo # your database name
secretKeys:
adminPasswordKey: password
userPasswordKey: password
existingSecret: external-secrets-db # yoursecret
I think docs are simply misleading 🙈 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I just updated from version 2.50.3 to the latest version. Up to this moment, i was connecting to an external postgre database in GCP, but since the last update im getting a "password authentication failed" error when trying to deploy. Here is an example of what i had until this update:
postgresql:
architecture: standalone
auth:
database: <db_name>
existingSecret: defectdojo-postgresql-specific
password: ""
secretKeys:
adminPasswordKey: postgresql-postgres-password
replicationPasswordKey: postgresql-replication-password
userPasswordKey: postgresql-password
username:
enabled: false
postgresServer:
....
extraEnv:
valueFrom:
secretKeyRef:
key: DD_DATABASE_URL
name: secret
The value of DD_DATABASE_URL was something like postgres://:@:/<db_name> with the password encoded with urlencoder.
In this update, i see that postgresServer was moved from postgresql.postgresServer. I did this change, but it still no working. I tried multiple things but none worked. Any idea of what the problem can be?
Beta Was this translation helpful? Give feedback.
All reactions