Class CloudEventEnvelope
- Namespace
- Ratatoskr.CloudEvents
- Assembly
- Ratatoskr.dll
CloudEvents envelope in structured content mode. See: https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#context-attributes
public class CloudEventEnvelope- Inheritance
-
CloudEventEnvelope
- Inherited Members
Properties
- Data
The event data (payload).
- DataContentType
[OPTIONAL] Content type of data value. This attribute enables data to carry any type of content, whereby format and encoding might differ from that of the chosen event format.
- DataSchema
[OPTIONAL] Identifies the schema that data adheres to. Incompatible changes to the schema SHOULD be reflected by a different URI.
- Extensions
Extension attributes (custom fields). Extension attributes MUST follow the same naming convention and use the same type system as standard attributes.
- Id
[REQUIRED] Identifies the event. Producers MUST ensure that source + id is unique for each distinct event. If a duplicate event is re-sent (e.g. due to a network error) it MAY have the same id. Consumers MAY assume that Events with identical source and id are duplicates.
- Source
[REQUIRED] Identifies the context in which an event happened. Often this will include information such as the type of the event source, the organization publishing the event or the process that produced the event. The exact syntax and semantics behind the data encoded in the URI is defined by the event producer.
- SpecVersion
[REQUIRED] The version of the CloudEvents specification which the event uses. This enables the interpretation of the context. Compliant event producers MUST use a value of "1.0" when referring to this version of the specification.
- Subject
[OPTIONAL] This identifies the subject of the event in the context of the event producer (identified by source). Identifying the subject of the event in context metadata is particularly helpful in generic subscription filtering scenarios.
- Time
[OPTIONAL] Timestamp of when the occurrence happened. Must adhere to RFC 3339.
- Type
[REQUIRED] This attribute contains a value describing the type of event related to the originating occurrence. Often this attribute is used for routing, observability, policy enforcement, etc. SHOULD be prefixed with a reverse-DNS name.