359 - One postgres instance for both keycloak and general database

[dimitur2204]

Solves #359

• Added a script to create a keycloak database on the current postgres instance.
• Changed the keycloak to now connect to the newly created database

Made the changes that @imilchev proposed in an old issue podkrepi-bg/infrastructure#17 in the infrastructure repo.
I don't know if it is still relevant though or if he is talking specifically about the infrastructure as code that is being deployed . In any case if it is needed in the infrastructure repo the solution should be similar

Notes:
There is a CREATE SCHEMA "public"; line in the init.sql file which I am unsure if is relevant in any way, but couldn't test it.

This is how the file structure in the pg-db container looks like:

Is that right considering we have 2 databases now @imilchev?

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	71.74%	1901/2650
🔴	Branches	46.44%	248/534
🔴	Functions	44.49%	222/499
🟡	Lines	69.84%	1686/2414

Test suite run success

180 tests passing in 64 suites.

Report generated by 🧪jest coverage report action from c717bc9

[igoychev]

nice and quick - thanks for helping Nizamov!
I was just thinking how we are going to do the migration now, because if we merge this it will redirect to the new empty database. So we need a migration script of some kind, don't we? - @imilchev what do you think?

[kachar]

Awesome upgrade @dimitur2204 🚀

[kachar]

I was just thinking how we are going to do the migration now, because if we merge this it will redirect to the new empty database. So we need a migration script of some kind, don't we? - @imilchev what do you think?

@igoychev I think this setup is only local via docker-compose, so the data exports will be for the testing data only, is that correct?

[dimitur2204]

I was just thinking how we are going to do the migration now, because if we merge this it will redirect to the new empty database. So we need a migration script of some kind, don't we? - @imilchev what do you think?

@igoychev I think this setup is only local via docker-compose, so the data exports will be for the testing data only, is that correct?

I am pretty sure this is the case for the code in this PR.

From what I understand from @imilchev his intention was to also do that on production though so that we only have 1 postgres instance to manage, however I think that will require help from him and everyone responsible for production!