Hi There, upon attempting to subscribe to an event that already exists, one would get the follow error back: [map[@odata.type:/redfish/v1/$metadata#Message.v1_0_0.Message Message:Subscription 'ResourceAdded event subscription' already exists. MessageId:Base.1.0.ResourceAlreadyExists Resolution:Do not repeat the create operation as the resource has already been created. Severity:Critical]] code:Base.1.0.ResourceAlreadyExists message:The requested resource already exists.]]
My question is: is it possible to include the id of the existing event in the http response so we can remove it and re-subscribe instead of erroring out?
There should be enough information included in the message arguments to identify the EventDestination resource - but if not, please post the contents of that message so we can see what is being implemented in that case. I would expect to see the EventDestination type, and the name/value of the "Destination" property as arguments - or perhaps "Id".
While it won't be something that will help with existing implementations, we do see the need for a new message that will point directly to the resource "in conflict" with one being created (attempted), so we'll add that to the Message Registry in the next version.