-
Notifications
You must be signed in to change notification settings - Fork 10
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
Provide health checks to allow docker to wait until the emulator is ready to receive requests #38
Comments
Note that we have also observed that the event hub emulator deletes all containers from the Azurite storage account, so if our tests also leverage Azurite they now need to wait arbitrarily before beginning, otherwise the emulator deletes the containers they use mid-run |
Hi @remoba, We have introduced health check API for Event hubs emulator in latest release. Please refer to release notes - https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-emulator-whats-new |
This has also been patched alongside addition of the Health-Check API. Now EH Emulator only cleans up its associated Tables & Blobs in Azurite. |
As noted in another ticket, this is good, but not quite enough to satisfy Docker Compose healthchecks. |
Is your feature request related to a problem? Please describe.
We're using docker compose to run the emulator. Sometimes after the docker image is up, it may take a few seconds for it to become available to accept requests. In other emulators we usually circumvent this by using health checks. For example, in Azurite we can do something like this the workaround suggested here Azure/Azurite#1666 (comment). However, this is not possible with the emulator as the image doesn't seem to contain an actual shell (sh / bash)
Describe the solution you'd like
Ideally a health check in the image itself, or some other best practice to follow
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: