Skip to content

Default database initialisation by backend server #114

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.

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

Open
tfrisk opened this issue Sep 25, 2020 · 1 comment · May be fixed by #122
Open

Default database initialisation by backend server #114

tfrisk opened this issue Sep 25, 2020 · 1 comment · May be fixed by #122
Labels
enhancement New feature or request

Comments

@tfrisk
Copy link
Contributor

tfrisk commented Sep 25, 2020

Is your feature request related to a problem? Please describe.
When creating a new installation from scratch, backend server fails to start if using fresh postgresql installation without any databases added.

Describe the solution you'd like
It would be nice if epimetheus backend server would create database with sensible defaults if it does not exist. This would help with our attempts to create an openshift template for epimetheus.

Describe alternatives you've considered
Alternative is to notice database is empty, notify user and frontend and then keep the backend server running. That would satisfy openshift as the pod would be kept running instead of going into crash loop.

Additional context
We are writing openshift template for epimetheus and this issue/feature is blocking our efforts.

@tfrisk tfrisk added the enhancement New feature or request label Sep 25, 2020
@tfrisk
Copy link
Contributor Author

tfrisk commented Sep 29, 2020

Backend works fine if I just remove this exit from backend code:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant