-
Notifications
You must be signed in to change notification settings - Fork 339
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
chore(*) generate DeepCopy interfaces #2222
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2222 +/- ##
==========================================
+ Coverage 51.77% 52.05% +0.28%
==========================================
Files 909 895 -14
Lines 41004 41041 +37
==========================================
+ Hits 21229 21364 +135
+ Misses 17741 17619 -122
- Partials 2034 2058 +24
Continue to review full report at Codecov.
|
@jakubdyszkiewicz WDTY about this approach? |
Enable DeepCopy interface generation for Kubernetes resources. This takes advantage of the fact that if a type already implementes the DeepCopy interface, deepcopy-gen will use it. This means that we can wrap the raw protbuf message fields in a type that supports the interface and then generate everything else. This updates #2130. Signed-off-by: James Peach <james.peach@konghq.com>
I'm ok with this. The bigger win here would be to do scaffolding for the whole policy with API, kumactl, K8S etc. etc., but that requires a couple of orders magnitude more effort than this. |
Enable DeepCopy interface generation for Kubernetes resources. This takes advantage of the fact that if a type already implementes the DeepCopy interface, deepcopy-gen will use it. This means that we can wrap the raw protbuf message fields in a type that supports the interface and then generate everything else. This updates #2130. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit fb4d537) # Conflicts: # mk/generate.mk
Yep, that would be great. I think we can get there, but baby steps :) |
Enable DeepCopy interface generation for Kubernetes resources. This takes advantage of the fact that if a type already implementes the DeepCopy interface, deepcopy-gen will use it. This means that we can wrap the raw protbuf message fields in a type that supports the interface and then generate everything else. This updates #2130. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit fb4d537) # Conflicts: # mk/generate.mk
Enable DeepCopy interface generation for Kubernetes resources. This takes advantage of the fact that if a type already implementes the DeepCopy interface, deepcopy-gen will use it. This means that we can wrap the raw protbuf message fields in a type that supports the interface and then generate everything else. This updates #2130. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit fb4d537)
Enable DeepCopy interface generation for Kubernetes resources. This takes advantage of the fact that if a type already implementes the DeepCopy interface, deepcopy-gen will use it. This means that we can wrap the raw protbuf message fields in a type that supports the interface and then generate everything else. This updates #2130. Signed-off-by: James Peach <james.peach@konghq.com> (cherry picked from commit fb4d537) Co-authored-by: James Peach <james.peach@konghq.com>
Summary
Enable DeepCopy interface generation for Kubernetes resources. This takes
advantage of the fact that if a type already implementes the DeepCopy
interface, deepcopy-gen will use it. This means that we can wrap the
raw protbuf message fields in a type that supports the interface and
then generate everything else.
This updates #2130.
Full changelog
N/A
Issues resolved
N/A
Documentation
N/A
Testing