-
Notifications
You must be signed in to change notification settings - Fork 59
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
Support SQLite database #345
Labels
feature
A new feature
Comments
mitchnielsen
changed the title
Support databases other than PostgreSQL
Support SQLite database
Jul 24, 2024
I bet this was indirectly addressed by https://github.com/PrefectHQ/prefect-helm/pull/365, but let's try it to be sure and add an SQLite test case to be sure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
In #336, we found that the database configuration was centralized within PostgreSQL - meaning database configuration couldn't be provided outside of the
postgresql
key, which matters if someone wants to use MySQL or even SQLite.Let's consider providing a new top-level key for configuring the database that's considered if
postgresql.enabled=false
.Notes
The Prefect docs mention:
Elsewhere, it says:
So realisticically, most users should be on PostgreSQL. But the documentation shows you how to use SQLite, so I think it's reasonable to support that configuration in the charts. As mentioned in #365, users are already using SQLite with the charts with some workarounds.
Acceptance criteria
postgresql
key if PostgreSQL is not in use.The text was updated successfully, but these errors were encountered: