Unable to override/set cloudevent properties with metadata during publishing about dotnet-sdk

[olitomlinson]

@JasonRodman

Given your example here :

var createdEvent = new SessionCreated();
new CloudEvent<SessionCreated>(createdEvent) { Type = "session-created" };

metadata = new Dictionary<string, string);
metadata.Add("cloudevent.id", createdEvent.Id);

await client.PublishEventAsync("messagebus", "Session", cloudEvent, metadata);

You could create your own CloudEvent (based on this ) and add an Id field, then you could do something like this :

new CloudEvent<SessionCreated>(createdEvent) { Type = "session-created", Id = createdEvent.Id };

My understanding (which could be wrong) is that when you specify a CloudEvent object, dapr will treat the model as-is, and won't attempt to interfere/augment it with other CE fields, (due to the content being set like this) So I think your metadata overrides are being ignored in this instance.

---

FWIW I can successfully override ce properties with this code, using redis :

request is just a normal serializable POCO (not a CloudEvent)

 
    var metadata = new Dictionary<string, string>();
    metadata.Add("cloudevent.id", "123");
    metadata.Add("cloudevent.type", "123");
    metadata.Add("cloudevent.source", "123");

    await daprClient.PublishEventAsync<StartWorkflowRequest>("kafka-pubsub", "workflowTopic", request, metadata, cts.Token);
      

this results in the following message body :

{
    "data": {
        ...
    },
    "datacontenttype": "application/json",
    "id": "123",
    "pubsubname": "redis-pubsub",
    "source": "123",
    "specversion": "1.0",
    "time": "2023-10-09T20:28:49Z",
    "topic": "workflowTopic",
    "traceid": "00-1c99e29b6f293df1836e945a1af06ffb-f4e20d12e31faa67-00",
    "traceparent": "00-1c99e29b6f293df1836e945a1af06ffb-f4e20d12e31faa67-00",
    "tracestate": "",
    "type": "123"
}

[olitomlinson]

@JasonRodman

A better answer is just to derive a new class which extends CloudEvent. Add any properties you require, CE or otherwise.

I.e. to include the ce field id you can just do this :

public class CloudEvent2<TData> : Dapr.CloudEvent<TData>
{
    public CloudEvent2(TData data) : base(data)
    {
        
    }

    [JsonPropertyName("id")]
    public string Id { get; init; }
}

var ce = new CloudEvent2<StartWorkflowRequest>(request) { 
    Id = "wf-" + Guid.NewGuid().ToString(),
    Source = new Uri("/cloudevents/spec/pull/123"), 
    Type = "my-type" };
    
await daprClient.PublishEventAsync<CloudEvent2<StartWorkflowRequest>>("redis-pubsub", "workflowTopic", ce, cts.Token);

which generates the following message body in pubsub

{
  "data": {
    "failOnTimeout": false,
    "id": "0-30"
  },
  "datacontenttype": "application/json",
  "id": "wf-6d632d55-5ddd-4c8e-be01-fb3c98e7abc5",
  "pubsubname": "redis-pubsub",
  "source": "/cloudevents/spec/pull/123",
  "specversion": "1.0",
  "subject": null,
  "time": "2023-10-11T12:01:58Z",
  "topic": "workflowTopic",
  "traceid": "00-d38ec30dbe1a3e7ad13430344cf62416-7996fe9086ffa58d-00",
  "traceparent": "00-d38ec30dbe1a3e7ad13430344cf62416-7996fe9086ffa58d-00",
  "tracestate": "",
  "type": "my-type"
}

[JasonRodman]

I will give that a try. So the crux of the problem is when you pass a CloudEvent or derived class to PublishEventAsync the metadata you pass it will be ignored. This behavior should probably be documented somewhere. The documentation leads me to think otherwise the way it currently reads.