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

[Change]: Move DB migrations to initContainers #2447

Open
ikreymer opened this issue Mar 1, 2025 · 0 comments · May be fixed by #2449
Open

[Change]: Move DB migrations to initContainers #2447

ikreymer opened this issue Mar 1, 2025 · 0 comments · May be fixed by #2449
Labels
enhancement New feature or request

Comments

@ikreymer
Copy link
Member

ikreymer commented Mar 1, 2025

What change would you like to see?

To avoid gunicorn worker timeouts / simplify init logic, the database migrations should be moved to an initContainers setup.

Context

Should fix issues raised in #2439

@ikreymer ikreymer added the enhancement New feature or request label Mar 1, 2025
ikreymer added a commit that referenced this issue Mar 1, 2025
- should avoid gunicorn worker timeouts for long running migrations, also fixes #2439
- add main_migrations as entrypoint to just run db migrations, using existing init_ops() call
- first run 'migrations' container with same resources as 'app' and 'op'
- additional typing for initializing db
- fixes #2447
ikreymer added a commit that referenced this issue Mar 1, 2025
- don't wait for languages to be ready to render UI
- catch if /api/settings returns an invalid response to show 'backend initializing' message
- will support initContainers where backend may return 5xx error via #2447
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Triage
Development

Successfully merging a pull request may close this issue.

1 participant