References:
CPS-877 - Getting issue details... STATUS
Overview
This user story is related to CPS-875 CM Handle State: Watchdog-process that syncs 'ADVISED' CM Handles.
Recap of watchdog process:
- Wake up on a specified schedule
- Identify node with state ‘ADVISED’
- Lock database, update timestamp, unlock the database
- Model sync
- Update state of the node to ‘READY’
As part of this story, only CM-Handles with a state of ready should be returned as part of queries or operations in regard to CM-Handles.
Issues and decisions
| # | Questions/Open Issues | Notes | Decision/Answer |
|---|---|---|---|
| 1 | Should state details be part of Response - get CM Handles Request | Don't think so. Check with Stakeholder | |
| 2 | Should filter be applied to the API which queries cm handles based on public properties | Check with Stakeholder | |
| 3 | Are all data API's which interact with CM-Handles affected by this - such as GET/POST/PATCH/DELETE operations | CPS-NCMP ↔ DMI-Plugin Interface Details Jakarta-R10 Also consider CPS-NCMP-I-01 | |
| 4 | What is the default value of a state if it is not specified when registering a cm-handle. | consider anything as NOT equals to 'READY' as NOT ready | 'ADVISED' |
List of API's and possible impact.