-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
HasMetadataOperation createVisitableBuilder #3284
Comments
Context #3070 |
I'm a little bit lost here.
I only see the Line 109 in 5751f31
I can't find that in the HasMetadataOperation class. Maybe you are referring to the static methods in the HasMetadata class? If this is the case, I don't think they can be consolidated. However, I'm a bit confused about the purpose of that field.
I think that, although it's a costly operation, we should probably use a serialize/deserialize (or convert to Map/Array+Map and back via Jackson) to stay on the safe side and avoid side-effects. |
Line 81 in 289a1ec
Used in Line 89 in 289a1ec
and Line 60 in 289a1ec
It sounds like we're in agreement to remove that latter usage. In looking at replacing the create method with handler logic, I see Line 124 in e1cc904
It appears to mean just the version. and Line 951 in e1cc904
That one only appears to be set by CustomResourceOperationsImpl and means the group + version. |
also just using serialization for cloning
also just using serialization for cloning
I added that method for edit operations - but I can see that it's possibly not needed given we should be able to lookup the Handler does that seem reasonable? Related to this there are apiVersion members/methods on both BaseOperation and HasMetadataOperation - should those be consolidated?
I'm also thinking it may not be a good idea to use the builder for cloning - just in case there are issues, like the one seen with CustomResource cloning, that would lead to really subtle bugs.
@rohanKanojia @manusa WDYT?
The text was updated successfully, but these errors were encountered: