-
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
Knative Generator Rewrite #2157
Knative Generator Rewrite #2157
Conversation
Can one of the admins verify this patch? |
ok to test |
6bb8cd1
to
f629b9c
Compare
Hey, thanks for already looking into this! I´d suggest pausing this for now, I´d rebase it on top of #2160 |
f629b9c
to
3b8b55e
Compare
…de proper scoping (namespaced vs cluster-wide) for all parts using the rewritten go generator. Changes: - go configuration requires scoping definition for all CRDs - marker interface 'Namespaced' added - go generator adds the marker interface to all Namespaced CRDs - during the generation of the *OperationsImpl, the marker interface is used to detect the proper scoping. This fixes fabric8io#2193
// no other types need to be defined as they are auto discovered | ||
crdLists := []reflect.Type{ | ||
|
||
// serving v1 |
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.
Umm, why have you removed all resources from duck v1beta1
. Are they not part of Knative model?
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.
2 things:
- all types that are only used internally are auto-discovered by the generator. Only CRDs need to be passed in as a starting point.
- AFAIK everything related to duck is not a CRD exposed by knative. Instead that is somehow used internally for duck typing. I might be wrong on this, do you have other information?
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.
Umm, I don't have much idea about Knative. I think it's okay if duck classes were not exposed earlier. I was just concerned if we could break something by dropping something that was present earlier.
3b8b55e
to
b1efad1
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
[merge] |
[knative]
[tekton]
[common]
As always, I´m looking forward to feedback!
Thanks,
Fabian