Skip to content

Comments

fix(metamcp): skip internal postgres config when using external DATABASE_URL#38

Merged
masterkain merged 3 commits intomainfrom
feat/metamcp-external-database-url
Feb 10, 2026
Merged

fix(metamcp): skip internal postgres config when using external DATABASE_URL#38
masterkain merged 3 commits intomainfrom
feat/metamcp-external-database-url

Conversation

@masterkain
Copy link
Member

Cherry-picks the change from #35 (external DATABASE_URL support) and bumps the chart version to satisfy chart-testing version gate.

Changes

  • Skip wait-db initContainer + internal postgres env/secret refs when values.env.DATABASE_URL is set.
  • Chart version: 0.2.1 -> 0.2.2 (patch bump).

Notes

balnibarbian and others added 2 commits February 10, 2026 08:41
…ASE_URL

When users provide `env.DATABASE_URL` to use an external PostgreSQL database,
the chart should not:
- Create the wait-db init container that waits for internal postgres
- Inject internal postgres environment variables (POSTGRES_HOST, PGHOST, etc.)
- Reference the internal postgres secret

This allows users to use external databases without needing to create
dummy secrets or deal with init containers waiting for non-existent services.

Fixes the issue where `postgres.enabled: false` with external `DATABASE_URL`
still required manual workarounds.
@masterkain masterkain merged commit 63e2a77 into main Feb 10, 2026
1 of 2 checks passed
@masterkain masterkain deleted the feat/metamcp-external-database-url branch February 10, 2026 07:52
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.

2 participants