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.
Screenshots/Logs
dial tcp [::1]:5432: connect: connection refused