It appears that the Refapp Distro Image gets built on every change and published to nightly. That is very cool. I’d like to create a dependent job, which starts a server using that image and a fresh MySQL database, waits for it to go all the way through initialization, and then saves the database container as a new image. We can then use this pre-initialized image for e.g. running E2E tests, making them run much faster.
Where does the job that publishes that Refapp Distro Image live? Is that something that one of our Bamboo jobs does?
What we need is to generate a database similar to the database in openmrs-spa server. So, is there a way to generate those data automatically, or is there any database container we could use?
@piumal1999 Yes, this is something that I thought would come up. What we need is to catalogue the data that are missing and we can easily add it via the Initializer module. One of the reasons for migrating off of the openmrs-spa server is precisely because replicating that database in a different context is very hard.
So, my question to you is: what concepts do we need? What provider details do we need?
I have a small doubt. In docker database configurations, I can’t see a pre-defined admin UUID. Does it mean that the admin uuid generates randomly? or is it defined somewhere else?