fix(dev-environment): Wait for Postgres to initialise before running CloudQuery #1034
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
akash1810
force-pushed
the
aa/dev-cq-works
branch
from
699b547
to
da5c920
Compare
akash1810
force-pushed
the
aa/dev-cq-works
branch
2 times, most recently
from
57ac443
to
e8bdcdc
Compare
Configure a healthcheck on the Postgres container, passing only once the initialisation scripts have completed. This fixes the behaviour where CloudQuery would fail stating: ```log failed to init destination postgresql: rpc error: code = Internal desc = failed to init plugin: failed to initialize client: failed to get current database: failed to connect to `host=postgres user=postgres database=postgres`: dial error (dial tcp 172.26.0.2:5432: connect: connection refused) ```
akash1810
force-pushed
the
aa/dev-cq-works
branch
from
e8bdcdc
to
4019e00
Compare
tjsilver
approved these changes
May 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
In the DEV environment, CloudQuery fails to connect to the Postgres database, logging:
This is because Postgres is still initialising when the connection is attempted. This initialisation includes creating the tables, and inserting rows copied from CODE.
In this change, a healthcheck is added to the Postgres container, passing only once the initialisation has completed. CloudQuery (and Grafana) starts afterwards.
Additionally, the configuration is updated, getting the CloudQuery container to connect to the Postgres container via the Docker network, as opposed to going via the host.
How has it been verified?
main, observe the above error from the CloudQuery container