Skip to content
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

Draft
wants to merge 343 commits into
base: main
Choose a base branch
from

Conversation

wind57
Copy link
Contributor

@wind57 wind57 commented Feb 7, 2023

No description provided.

* @author wind57
*/
@Configuration
public class KubernetesDiscoveryClientHealthConfiguration {
Copy link
Contributor Author

@wind57 wind57 Feb 7, 2023

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)

@wind57 wind57 changed the title fix move blocking health bean to a separate configuration Feb 7, 2023
@wind57 wind57 changed the title move blocking health bean to a separate configuration move blocking health bean to a separate configuration (CAN ONLY GO IN THE NEXT MAJOR RELEASE) Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants