-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 static state to non-static #3875
Comments
After 3858 the change can be achieved by switching Adapters and Handlers from utility to regular instantiable classes. |
Switching Adapters to be non-static is straight-forward - especially if we ignore being able to directly call register/unregister. Handlers is much more involved - it has a lot more usage and from places that don't currently have a reference to the client. |
TBH I only checked the Adapters part. Maybe we can split the issue in 2. |
I think I should work this after #3955 as it will be another large change - we'll either have to expand or remove the ClientContext. |
- converting openshift clients to extension api - removing extension adapters as extension client adapters can act as their own factories - correcting namespaced/plural for several openshift resources to remove their operations
- converting openshift clients to extension api - removing extension adapters as extension client adapters can act as their own factories - correcting namespaced/plural for several openshift resources to remove their operations
Is your task related to a problem? Please describe
Adapters and Handlers are currently static, which creates problematic references to things like classloaders.
Describe the solution you'd like
They should be moved to state on the KubernetesClientBuilder or whatever we eventually settle on for that construct.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: