-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Update API slice fields to not use pointers #9802
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet 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 |
/hold for comment |
/lgtm |
/test pull-kops-e2e-k8s-containerd |
/test pull-kops-e2e-k8s-containerd |
079718b
to
ca790db
Compare
/test pull-kops-e2e-k8s-containerd |
ca790db
to
2b39b42
Compare
/test pull-kops-e2e-k8s-containerd |
2b39b42
to
bffa68a
Compare
/test pull-kops-e2e-k8s-containerd |
/lgtm |
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.
I think using a pointer to a slice member would reduce the number of changes.
bffa68a
to
e57045b
Compare
Updated to use pointers when modifying elements in a for loop. diff looks much cleaner now 👍 |
This is causing problems with the Kubernetes 1.19 code-generator. A nil entry in these slices wouldn't be valid anyways, so this should have no impact.
e57045b
to
7d9f0a0
Compare
/hold cancel |
/lgtm |
/test pull-kops-e2e-kubernetes-aws |
/retest |
A slice of pointers causes problems with the Kubernetes 1.19 code-generator.
A nil entry in these slices isn't valid anyways, so this should have no impact short of being a breaking change for anyone importing these API types.