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
Ensure KubernetesInformerFactoryProcessor does not access any beans #1532
Conversation
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.
Great starter. Still IMO needs some polishing.
...java/io/kubernetes/client/spring/extended/controller/KubernetesInformerFactoryProcessor.java
Show resolved
Hide resolved
...java/io/kubernetes/client/spring/extended/controller/KubernetesInformerFactoryProcessor.java
Outdated
Show resolved
Hide resolved
...java/io/kubernetes/client/spring/extended/controller/KubernetesInformerFactoryProcessor.java
Outdated
Show resolved
Hide resolved
...java/io/kubernetes/client/spring/extended/controller/KubernetesInformerFactoryProcessor.java
Outdated
Show resolved
Hide resolved
...st/java/io/kubernetes/client/spring/extended/controller/KubernetesReconcilerCreatorTest.java
Show resolved
Hide resolved
...java/io/kubernetes/client/spring/extended/controller/KubernetesInformerFactoryProcessor.java
Outdated
Show resolved
Hide resolved
b498e2b
to
e6b964e
Compare
A `BeanDefinitionRegistryPostProcessor` should not ideally refer to any bean instances, except lazily. This change makes the bean definitions that are installed by an `<at>KubernetesInformer` lazier by putting them behind a `Supplier` Signed-off-by: Dave Syer <dsyer@vmware.com>
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.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dsyer, yue9944882 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
A
BeanDefinitionRegistryPostProcessor
should not ideally refer to anybean instances, except lazily. This change makes the bean definitions
that are installed by a
@KubernetesInformer
lazier by putting thembehind a
Supplier
See also #1516