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.

Sign up for GitHub

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

Jump to bottom

[v2] Change to database config #3600

Closed
adlerhurst opened this issue May 5, 2022 · 5 comments · Fixed by #3998
Closed

[v2] Change to database config #3600

adlerhurst opened this issue May 5, 2022 · 5 comments · Fixed by #3998
Assignees
@adlerhurst
Labels
backend lang: go Pull requests that update Go code

Comments

@adlerhurst
Copy link
Member

Add possibility to define the database type in the configuration of ZITADEL.
@adlerhurst adlerhurst added task lang: go Pull requests that update Go code backend labels May 5, 2022
@adlerhurst adlerhurst mentioned this issue May 5, 2022
Open
2 tasks
@AmreeshTyagi
Copy link

AmreeshTyagi commented Jun 21, 2022 •
edited

Hi, any plan to initiate discussion on this in near future?

Actually, I want to use Zitadel, but we are on MySQL stack, so using CRDB is not easy at the moment for us.

@hifabienne
Copy link
Member

Hi @AmreeshTyagi

We don't have a timeline yet for this. Probably we will have a look at this in 1-2 months.
Its planned to start with the possibility to use Postgres as DB.

@adlerhurst adlerhurst linked a pull request Jul 19, 2022 that will close this issue
feat(database): support for postgres #3998
Merged
@adlerhurst
Copy link
Member Author

hi @AmreeshTyagi

The transition to non postgres compatible databases will take more time. This issue is used to track the changes of the configuration. I link your comment in this issue: #3598

@fforootd fforootd changed the title [v2] config [v2] Change to database config Jul 19, 2022
@AmreeshTyagi
Copy link

ok. I understand. Providing postgres compatible first is an obvious choice because of driver compatibility.

Would be waiting for MySQL plan. Thanks for the response.

@livio-a
Copy link
Member

livio-a commented Aug 2, 2022

closing this as we did the config changes in #4068 and generell database support is tracked in #3598 and postrges #3898

@livio-a livio-a closed this as completed Aug 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adlerhurst adlerhurst

Labels
backend lang: go Pull requests that update Go code
Projects
No open projects
Kanban
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(database): support for postgres zitadel/zitadel
4 participants
@AmreeshTyagi @livio-a @adlerhurst @hifabienne