...
...
...
...
...
...
Table of Contents |
---|
References
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
# | Issue | Notes | Decision |
---|---|---|---|
1 | List scenarios | Need to clarify scenarios | Refer to Internal study |
2 | Topics | what topics are used in what scenario (topic for each Datastore ?) | See Topics section below.
cm-events topic name should be configurable in deployment settings.
|
3 | Handle unknown event schemas | Wrap event? | Unsupported for now. Thrown exception and log error. |
Event Flow
...
Overview
CM Event Specification Outline
{ "eventId" : "9999", # some generic event uuid generated by DMI Plugin "event": { } |
---|
RFC 8641 : yang-datastore notification definition
notifications: +---n push-update | +--ro id? sn:subscription-id | +--ro datastore-contents? <anydata> | +--ro incomplete-update? empty +---n push-change-update {on-change}? +--ro id? sn:subscription-id +--ro datastore-changes | +--ro yang-patch | +--ro patch-id string | +--ro comment? string | +--ro edit* [edit-id] | +--ro edit-id string | +--ro operation enumeration | +--ro target target-resource-offset | +--ro point? target-resource-offset | +--ro where? enumeration | +--ro value? <anydata> +--ro incomplete-update? empty |
---|
'operation' type definition
Event Payload Example
Proposed CM event |
---|
{ "eventId" : "9999", # some generic event uuid generated by DMI Plugin "event": { "push-change-update" : { "datastore-changes" : { {
} } } |
...