-
Notifications
You must be signed in to change notification settings - Fork 611
Closed
Labels
area/apiarea/brokersarea/channelskind/feature-requesttriage/acceptedIssues which should be fixed (post-triage)Issues which should be fixed (post-triage)
Description
Problem
It would be nice if "developers" can enforce on the Broker
level some (simple) rules on:
- what events can be consumed
- who is the sending identity (see also OIDC proposal)
For more details refer to the feature track document: https://docs.google.com/document/d/1u6vyMviGpD13uyLKSGV7_D_p0ZRBPWg6PlLItRH8UFI/edit
This feature request / issue related to:
- OIDC proposal for defining the
who
part
Some details:
- return a
403
error code, if the event type is not part of the list (see here) - we could support wildcards, such as
dev.knative.*
... If folks really want that... - In the case of a provide lists of event types, and a
Trigger
registered for the broker is specifing a different event type: TheTrigger
would not go toready: true
state
Persona:
Developers
Exit Criteria
Feature implemented and tests
Shashankft9
Metadata
Metadata
Assignees
Labels
area/apiarea/brokersarea/channelskind/feature-requesttriage/acceptedIssues which should be fixed (post-triage)Issues which should be fixed (post-triage)
Type
Projects
Status
Done
Status
Done