specs
specs copied to clipboard
knative
Knative specs and conformance tests
# Changes - Adding `403` response code explicitly, in case of "not allowed" events /kind Fixes # **Release Note** ```release-note ``` **Docs** ```docs ```
Added timeout to the delivery spec. For more details: knative/eventing#5149
Document management of `status.observedGeneration` and client behavior from [this comment](https://github.com/knative/specs/pull/25#issuecomment-885147111). TODO: experiment whether mutating webhooks could actually clear Conditions during PATCH of `spec`. If so, update webhooks and then we...
With the new enhanced event filtering/subscriptionsapi filtering moving to GA in the next release, it should be documented in the spec.
Based on https://github.com/knative/specs/issues/102 There is interest in doing more, than those three attributes. See here https://github.com/knative-sandbox/eventing-kafka-broker/issues/2376 One way to address this, is to allow some standardized http header prefix, and...
Some channel implementations do enhance the CloudEvents in the case they are forwarding them to the configured Dead Letter Sink. Details can be read here: https://knative.dev/docs/eventing/event-delivery/#configuring-channel-event-delivery - The behavior is...
This issue is to discuss whether First In First Out (FIFO) or ordered events should be something that's configurable through the spec. The prominent implementations of Broker/Trigger currently already support...
The [Channel lifecycle specification](https://github.com/knative/specs/blob/main/specs/eventing/control-plane.md#channel-lifecycle) doesn't include the desired behavior of the status.deadLetterSinkURI (as the Trigger does). It should be added to it's spec (as optional at least)
The [source specification](https://github.com/knative/eventing/blob/main/docs/spec/sources.md) hasn't been moved to the repository (yet). At the minimum the specification should include the source duck type (in the document linked above). I believe specific sources,...
There is a line in the control plane spec: > Triggers MUST be associated with a Broker based on the `spec.broker` field on the Trigger; which reads to me that...
