| Table of Contents |
|---|
Overview
Jira Legacy
| Table of Contents |
|---|
Overview
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
CNCF Cloud Event alignment
Introduction
CNCF CloudEvents is a specification for describing event data in common formats to provide interoperability across services, platforms and systems.
- These cloud events will be applied to all the internal and external events we have in CPS , NCMP and DMI Plugin.
- Cloud events will be taking care of the fields which are part of Headers or part of the actual payload (fields other than "data" are sent as Headers)
- These CNCF cloud events will be applied to all the events listed in above sections (LCM , DMI Data AVC etc.)
...
Before | After1 | CloudeEvent builder method | Example Value | Notes | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
eventId | (ce_)id | .withId() | Mandatory | |||||||||||||||||||
eventSource | (ce_)source | .withSource() | Mandatory | |||||||||||||||||||
N/A | (ce_)specversion (default 1.0) | .v1() | 1.0 | Mandatory - This is the version of the cloud events | ||||||||||||||||||
eventType | (ce_)type | .withType() | Mandatory | eventTime)type | .withType() | Mandatory | ||||||||||||||||
eventTime | (ce_)time | .withTime() | Optional (could be Mandatory for | |||||||||||||||||||
eventSchema | (ce_)dataschema | .withDataSchema() | Optional includes the version of the schema | |||||||||||||||||||
| content-type2 | withDataContentType() | application/json | Optional | |||||||||||||||||||
| eventCorrelationId | (ce_) | timecorrelationid | . | withTimewithExtension() | Optional | (could be Mandatory for eventSchema | (ce_)dataschema | .withDataSchema() | Optional includes the version of the schema | content-type2 | withDataContentType() | application/json | Optional | eventCorrelationId | (ce_)correlationid | .withExtension() | Optional This will be part of the extensions field in the cloud events and all the restrictions of the attribute field naming applies to it. i.e these fields will be in the small case. This is marked as optional as it only applies to some events. | event | (ce_)data | .withData(json TBC) | Mandatory actual event/payload now would be under "data" field. |
...
This will be part of the extensions field in the cloud events and all the restrictions of the attribute field naming applies to it. i.e these fields will be in the small case. This is marked as optional as it only applies to some events. | ||||
| event | (ce_)data | .withData(json TBC) | Mandatory actual event/payload now would be under "data" field. |
- Note 1 all cloud-event headers will be prefixed during serialization with 'ce_' (this means when filtering on serialized Kafka-headers this prefix need to be applied)
- Note 2 content-type is a a 'default' header name no 'wrapped' by CloudEvents and hence the inconsistency in names and that is does NOT have the 'ce_' prefix.
Common NCMP response staus code & message :
- Status-code 0-99 is reserved for any success response
- Status-code from 100 to 199 is reserved for any failed response.
Status Code | Status Message |
|---|---|
| 1 | Successfully applied changes. |
100 | cm handle id(s) is(are) not found. |
| 101 | cm handle id(s) is(are) in non ready state. |