-
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
Tekton OperationsImpl Scope Fix #2194
Conversation
…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
Can one of the admins verify this patch? |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
ok to test |
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.
Looks good, Thanks.
But I see you have only made changes in tekton. Are you planning to change Knative, ServiceCatalog and Kubernetes Model after this patch?
@Fabian-K : Bdw, I've started to document client operations in our cheat sheet. Would appreciate if you could contribute some documentation regarding tekton extensions there 🙏 |
I just rebased my knative pr on top of this one and included the scoping info there as well. (although there are no cluster-scoped CRDs in knative) When other modules like ServiceCatalog or K8s core uses the generator rewrite, they are forced to include it by the go compiler :) The cheat sheet looks nice! Will try to find some time for tekton :) |
[merge] |
This PR updates the generation logic for *OperationsImpl to include proper scoping (namespaced vs cluster-wide) for all parts using the rewritten go generator.
Changes:
This fixes #2193