-
Notifications
You must be signed in to change notification settings - Fork 630
Trigger status depends on importer status #1849
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
Changes from all commits
b7f8803
76fa667
da23a43
6d5163f
41fc57a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,79 @@ | ||
| # Copyright 2019 The Knative Authors | ||
| # | ||
| # Licensed under the Apache License, Version 2.0 (the "License"); | ||
| # you may not use this file except in compliance with the License. | ||
| # You may obtain a copy of the License at | ||
| # | ||
| # http://www.apache.org/licenses/LICENSE-2.0 | ||
| # | ||
| # Unless required by applicable law or agreed to in writing, software | ||
| # distributed under the License is distributed on an "AS IS" BASIS, | ||
| # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| # See the License for the specific language governing permissions and | ||
| # limitations under the License. | ||
|
|
||
| # Use this aggregated ClusterRole when you need readonly access to "Sources" | ||
| apiVersion: rbac.authorization.k8s.io/v1 | ||
| kind: ClusterRole | ||
| metadata: | ||
| name: source-resolver | ||
| labels: | ||
| eventing.knative.dev/release: devel | ||
| aggregationRule: | ||
| clusterRoleSelectors: | ||
| - matchLabels: | ||
| duck.knative.dev/sourceObserver: "true" | ||
| rules: [] # Rules are automatically filled in by the controller manager. | ||
|
|
||
| --- | ||
|
|
||
| kind: ClusterRole | ||
| apiVersion: rbac.authorization.k8s.io/v1 | ||
| metadata: | ||
| name: eventing-source-resolver | ||
| labels: | ||
| eventing.knative.dev/release: devel | ||
| duck.knative.dev/sourceObserver: "true" | ||
| # Do not use this role directly. These rules will be added to the "source-resolver" role. | ||
| # For resources "awssqssources", "camelsources", "kafkasources", "githubsources", | ||
| # These should eventually be moved to config directories in https://github.com/knative/eventing-contrib. | ||
| # TODO After https://github.com/knative/eventing-contrib/issues/583 gets done, remove "awssqssources", "camelsources", "kafkasources", "githubsources" in resources and modified config/201-clusterrolebinding.yaml | ||
| rules: | ||
| - apiGroups: | ||
| - "sources.eventing.knative.dev" | ||
| resources: | ||
| - "cronjobsources" | ||
| - "containersources" | ||
| - "apiserversources" | ||
| - "awssqssources" | ||
|
capri-xiyue marked this conversation as resolved.
|
||
| - "camelsources" | ||
| - "kafkasources" | ||
| - "githubsources" | ||
| verbs: | ||
| - get | ||
| - list | ||
| - watch | ||
| --- | ||
|
|
||
| # These should eventually be moved to config directories in https://github.com/google/knative-gcp. | ||
| # TODO After https://github.com/google/knative-gcp/issues/252 gets done, remove this ClusterRole and modified config/201-clusterrolebinding.yaml | ||
| kind: ClusterRole | ||
| apiVersion: rbac.authorization.k8s.io/v1 | ||
| metadata: | ||
| name: knative-gcp-source-resolver | ||
| labels: | ||
| eventing.knative.dev/release: devel | ||
| duck.knative.dev/sourceObserver: "true" | ||
| # Do not use this role directly. These rules will be added to the "source-resolver" role. | ||
| rules: | ||
| - apiGroups: | ||
| - "pubsub.cloud.run" | ||
| - "events.cloud.run" | ||
| resources: | ||
| - "pullsubscriptions" | ||
|
capri-xiyue marked this conversation as resolved.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same question about status subresources.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We don't need to update status. Do we need the status subresources? I did manual testing. It works even without permission of status subresources. |
||
| - "storages" | ||
| verbs: | ||
| - get | ||
| - list | ||
| - watch | ||
| --- | ||
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.
Do we need the status subresource as well? E.g.
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 no, because we never write the status.
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.
Makes sense. Probably worth giving this feedback on #1856, which says they must include the status subresources.