-
Notifications
You must be signed in to change notification settings - Fork 210
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
Having the same type embedded more than once breaks generation #129
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
Does it make sense for me to tackle this as my first contribution? |
Add the code link with SHA https://github.com/openshift/api/blob/86cb5b750830da685a27b7e983971270c9c6f5f6/servicecertsigner/v1alpha1/types.go#L15-L21 @enj Do you think we still need to handle this case as the API has changed to no embedding. |
ServiceServingCertSignerConfig
embedsmetav1.TypeMeta
andconfigv1.GenericControllerConfig
: https://github.com/openshift/api/blob/master/servicecertsigner/v1alpha1/types.go#L15-L21At the time,
configv1.GenericControllerConfig
also embeddedmetav1.TypeMeta
, which led to:The text was updated successfully, but these errors were encountered: