-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Feature: Docker Host Retry #19127
Feature: Docker Host Retry #19127
Conversation
Hi there 👋 Thanks for your contribution! The OpenMetadata team will review the PR shortly! Once it has been labeled as Let us know if you need any help! |
…_docker_host decorator
…into feature/dockerhost-retry
…re creating source class
…into feature/dockerhost-retry
…into feature/dockerhost-retry
if "localhost" in host_port_str: | ||
result = test_connection_fn(metadata, connection, request.connection.config) | ||
raise_test_connection_exception(result) | ||
|
||
test_connection_fn( | ||
metadata, connection, request.connection.config, automation_workflow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this mean we run the test connection twice in case of localhost and when no exception is thrown?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we need to do this to show the result of test_connection on the frontend
…into feature/dockerhost-retry
Quality Gate passed for 'open-metadata-ingestion'Issues Measures |
Describe your changes:
I implemented a retry mechanism for the service connection, replacing localhost with host.docker.internal if a connection error occurs.
Type of change:
Checklist:
Fixes <issue-number>: <short explanation>