Skip to content

fix(helm): allow externalSecret as valid DATABASE_URL source in postgres validation#3421

Merged
o-pauloroberto merged 1 commit into
mainfrom
fix/helm-validate-external-secret-postgres
May 21, 2026
Merged

fix(helm): allow externalSecret as valid DATABASE_URL source in postgres validation#3421
o-pauloroberto merged 1 commit into
mainfrom
fix/helm-validate-external-secret-postgres

Conversation

@o-pauloroberto
Copy link
Copy Markdown
Collaborator

@o-pauloroberto o-pauloroberto commented May 21, 2026

Problem

When database.engine=postgresql and externalSecret.enabled=true, the chart fails at render time:

chart-deco-studio: defina database.url quando database.engine=postgresql ou use secret.secretName para fornecer DATABASE_URL via Secret

The validation only accepted database.url or secret.secretName as valid sources for DATABASE_URL, ignoring the case where the value comes from AWS Secrets Manager via ExternalSecret.

Fix

Added externalSecret.enabled as a third valid source. The check now passes when any of these is set:

  • database.url
  • secret.secretName
  • externalSecret.enabled: true

Republishes chart 0.7.0 with the fix included.


Summary by cubic

Fix Helm chart validation to accept externalSecret.enabled as a valid DATABASE_URL source when database.engine=postgresql, preventing render failures for ExternalSecret setups (e.g., AWS Secrets Manager). The chart now renders without requiring database.url or secret.secretName when ExternalSecret is used.

Written for commit 78d3783. Summary will update on new commits. Review in cubic

@o-pauloroberto o-pauloroberto merged commit edae986 into main May 21, 2026
14 checks passed
@o-pauloroberto o-pauloroberto deleted the fix/helm-validate-external-secret-postgres branch May 21, 2026 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant