Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Add credential templates in migration job when using existing DB #6792

Merged

Conversation

stevencrake-nscale
Copy link
Contributor

@stevencrake-nscale stevencrake-nscale commented Nov 18, 2024

Title

Fix migration job failing for existing databases.

Relevant issues

Fixes #6791

Type

🐛 Bug Fix

Changes

If the chart is configured to use an existing database, the migration job will pull the necessary database credential information from secrets within the cluster. This follows the same pattern that the Deployment template currently uses.

Copy link

vercel bot commented Nov 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
litellm ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 25, 2024 3:05pm

@stevencrake-nscale stevencrake-nscale force-pushed the fix/migration-db-useExisting branch from 8a00ceb to 3bf9003 Compare November 25, 2024 15:04
@stevencrake-nscale stevencrake-nscale changed the title fix: migration job for existing db fix: Add credential templates in migration job when using existing DB Nov 26, 2024
@justinthelaw
Copy link

Related to #6985, since previous issue was closed, and I'd like to track this PR and fix

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.

[Bug]: migration fails when .Values.db.useExisting is true
3 participants