Create microservices' database dynamically about minos-cli HOT 4 CLOSED

In our daily @garciparedes has pointed out that creating the database on microservices' startup means giving them permission to create databases but also to delete them. This might create problems since a microservice might delete others databases.

from minos-cli.

Maybe just giving creation permission to every microservice might do the trick?

Another options, as we've discussed, is to create databases from an admin microservice or panel.

Any further ideas? @Clariteia/core-devs 🤔

from minos-cli.

Hi @albamig, I agree with you in the sense that having to create databases manually is an awful task, and even more if it requires restarting the database container (like in the case of our docker-compose.yml examples).

My proposal here is to have an outer configuration layer with that responsibility (as it's not only a microservice setup, but an environment one). Maybe that tool could be able to manage both database creations and also the roles to access them. Thinking about that, I'm getting another interesting use cases for this management tool such as key generation for secure connections among microservices and so on. I think this kind of tasks could fit within the minos-cli package. 🙂

from minos-cli.

According to the lasts decisions related with this topic (the database creation process should be performed by the microservice generator), I'll proceed transferring to the https://github.com/Clariteia/minos repository

from minos-cli.