-
Notifications
You must be signed in to change notification settings - Fork 422
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
Add Namespaced Scope Interceptor #1462
Conversation
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.
/hold
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/hold cancel |
The following is the coverage report on the affected files.
|
/test pull-tekton-triggers-integration-tests |
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.
/kind feature
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
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.
The code looks fine, but I think we should add examples and docs before the release
If a clusterinterceptor and interceptor have the same name, which one is used?
I didn't get this. Which place are you talking about? We specify InterceptorKind in the ref. |
Is InterceptorKind a required field now? And does it default to ClusterInterceptor? |
It's still optional. By default, it is ClusterInterceptor. Added documentation. I will add examples soon. |
The following is the coverage report on the affected files.
|
got it, that makes sense! |
I will add the example on Monday. |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dibyom 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 |
7ead05d
to
b79e0a6
Compare
The following is the coverage report on the affected files.
|
Added Namespaced Scope Interceptor. A namespaced admin can create and manage its interceptor without requiring elevated permissions. Fixes #1364
b79e0a6
to
c165271
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
@savitaashture I have added the example. Please review and add LGTM. |
Example utilizes Core Interceptor from v0.19 Triggers.
315196d
to
2d31171
Compare
The following is the coverage report on the affected files.
|
/lgtm |
Added Namespaced Scope Interceptor. A namespaced admin can create and manage its interceptor without requiring elevated permissions. Fixes #1364
Changes
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Release Notes