Test Case | Description | Status | Owner | Date | JIRA link | Comment |
data-router | v1 | orchestration-event-service | orchestration-event | Verify that the orchestration-event API operation only needs to be provided the serviceInstanceId, modelVersionId and modelInvariantId parameters |
| |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-428 |
---|
|
|
|
data-router | orchestration-event-service | orchestration-event | Verify that the latest version (v1) of the orchestration-event operation is invoked when the API version is not explicitly specified. |
| |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-428 |
---|
|
|
|
data-router | orchestration-event-service | orchestration-event | Verify that if the v1 API is used to send an orchestration-event operation and the two deprecated parameters – customerId and serviceType – are included, either a POA-AUDIT-INIT message is written without the offending parameters or the request is entirely rejected. |
| |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-428 |
---|
|
|
|
POA-AUDIT-RESULT | processing | Verify that the Data Router remains capable of consuming and processing POA-AUDIT-RESULT events. |
| |
| Jira Legacy |
---|
server | System Jira |
---|
serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
---|
key | LOG-428 |
---|
|
|
|