-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
improve lookup server behaviour #13401
Conversation
Don't try to connect to the lookup server if the lookup server was disabled by the admin or an empty lookup server URL was given Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
@schiessle ping |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
@rullzer from my pov this is ready to go in after my last commits from yesterday |
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.
Code makes sense 👍
CI failure unrelated |
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.
Lets do this then
Should we backport this? I guess it would make sense. |
/backport to stable15 |
backport to stable15 in #14696 |
Don't try to connect to the lookup server if the lookup server was disabled
by the admin or an empty lookup server URL was given
fix #13396
Additionally we should consider to add a background job which clean existing data from the lookup sever once the admin disabled it, see #13396 (comment)