...
Jira Legacy server System Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key CPS-2022
Issues & Decisions
# | Issue | Notes | Decisions |
|---|---|---|---|
| 1 |
Overview
This is internal page intended for the collaboration between the team to decide how the Subscription will be present in memory.
Proposed Structure
| Code Block | ||
|---|---|---|
| ||
Map < Unique Subscription Id , Map < Dmi-Plugin Name , CmSubscriptionCompositeObject > >
CmSubscriptionCompositeObject
- List of cmHandles - Subscription request incoming cmhandles grouped using target dmiPlugin
- Status ( Accepted , Rejected or Pending ) - initially Pending
- Datastore ( passthrough-operational and passthrough-running )
- List of xpaths |
Example
| Code Block |
|---|
{"subscription123" , { "dmi-1" : { “targetFilter” : list of cmhandles, // mandatory "scopeFilter" : { "datastore": “ncmp-datastore:passthrough-operational or ncmp-datastore:passthrough-running", // optional. default is passthrough-operational "xpath-filter": list of valid xpaths // mandatory }, "status" : "ACCEPTED/REJECTED/PENDING" } } } |