Closed Ziabatcha closed 9 months ago
Issue not observed with [Test_v1.1.2]. Observing 204 response for API 'http://XXX:XXX/v1/regard-device-object-creation'
{"notification-proxy-1-0:object-creation-notification":{"counter":17,"timestamp":"2024-02-14T05:56:13.0+00:00","object-path":"/core-model-1-4:network-control-domain=live/control-construct=513250009/forwarding-domain=VLAN-FD/fc=VLAN-3332"}}
http://xxx:xxx/v1/regard-device-object-creation
curl -X POST "http://xxx:xxx/v1/regard-device-object-creation" -H "accept: application/json" -H "user: User Name" -H "originator: Resolver" -H "x-correlator: 550e8400-e29b-11d4-a716-446655440000" -H "trace-indicator: 1.3.1" -H "customer-journey: Unknown value" -H "operation-key: Operation key not yet provided." -H "Content-Type: application/json" -d "{\"notification-proxy-1-0:object-creation-notification\":{\"counter\":17,\"timestamp\":\"2024-02-14T05:56:13.0+00:00\",\"object-path\":\"/core-model-1-4:network-control-domain=live/control-construct=513250009/forwarding-domain=VLAN-FD/fc=VLAN-3332\"}}"
When Object creation notification is received on API:/v1/regard-device-object-creation, observing error 500 in MWDI.