Skip to content
This repository has been archived by the owner. It is now read-only.

Edge case: DB already populated #16

Closed
ghost opened this issue Sep 19, 2016 · 1 comment
Closed

Edge case: DB already populated #16

ghost opened this issue Sep 19, 2016 · 1 comment

Comments

@ghost
Copy link

ghost commented Sep 19, 2016

During testing, it's possible to have containers run for the first time, but to use db volume contents that mean the DB has already been created. (This will be possible in the real world, too.)

In the event that the database already has a schema created, the schema creation should be skipped.

@ghost ghost closed this as completed in 650e808 Sep 20, 2016
ghost pushed a commit that referenced this issue Sep 20, 2016
Added capability to detect schema needs, closes #16
@ghost
Copy link
Author

ghost commented Sep 21, 2016

in which step do you check if mariadb have the users created, because I saw in the last commit 650e808 , the step that check if database have user/password for database are ready was removed. Now only check if mariadb is up an running but did not check if mariadb have users and databases creates , example (registry database with the correct user). One posible error can appear if mariadb start first comanage but user is not created at time that commonage make any connection trying to use the user that need to connect mariadb.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants