-
Notifications
You must be signed in to change notification settings - Fork 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
move blocking health bean to a separate configuration (CAN ONLY GO IN THE NEXT MAJOR RELEASE) #1212
base: main
Are you sure you want to change the base?
move blocking health bean to a separate configuration (CAN ONLY GO IN THE NEXT MAJOR RELEASE) #1212
Conversation
* @author wind57 | ||
*/ | ||
@Configuration | ||
public class KubernetesDiscoveryClientHealthConfiguration { |
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.
since both fabric8 and k8s-native clients use the same exact bean, I decided to move them to a separate configuration and @Import
it in the proper configs. Since we already had proper tests, by not failing, they proved that @Import
respects AutoConfigureAfter and various @conditional(s)
No description provided.