You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently, the application starts without the knowledge of the DB connection. If the downstream DB is down, we get to know only when we hit the API.
To Reproduce
Start the application with a wrong DB connection
Application starts
Call any API, fails with DB connection is not available.
Expected behavior
The application should not start if the DB connection is not possible.
Okay, thanks @tejash-jl. Let me take a shot at it.
I'm thinking of introducing Ping function to repository.DBInterface and call pg.DB.Ping from postgres.Ping. Let me know if you can think of a better way.
Describe the bug
Currently, the application starts without the knowledge of the DB connection. If the downstream DB is down, we get to know only when we hit the API.
To Reproduce
Expected behavior
The application should not start if the DB connection is not possible.
Screenshots/Logs
dial tcp [::1]:5432: connect: connection refused
The text was updated successfully, but these errors were encountered: