[Custom Handlers]Metadata of DateTime type is serialized as string

[ZachTB123]

When creating a function with a ServiceBus input and logging the InvokeRequest, I am seeing something like the following in App Insights:

&{Data:map[queue:base64EncodedDataRedacted] Metadata:map[ContentType:"text/plain" DeliveryCount:11 EnqueuedTimeUtc:"2020-08-31T16:48:37.708Z" ExpiresAtUtc:"9999-12-31T23:59:59.9999999" LockToken:"7ebe3bcf-bae7-455e-99ea-568500a75173" MessageId:"883052175d7f490083127c81826fce10" ... (rest is omitted)]}

Notice that there are some keys in the Metadata map (e.g. ContentType, EnqueuedTimeUtc, LockToken, etc.) that have their values wrapped in double quotes (""). Note I've seen the trigger input (in this case queue) behave the same way (wrapped in double quotes) but have gotten around this by setting "dataType" to "binary" in the function.json file.

This is causing issues when I try and unmarshal this metadata map into a Golang struct where EnqueuedTimeUtc is of type time.Time:

type ServiceBusMessageMetadata struct {
	DeliveryCount   int       `json:"DeliveryCount,string"`
	EnqueuedTimeUtc time.Time `json:"EnqueuedTimeUtc"`
	ExpiresAtUtc    string    `json:"ExpiresAtUtc"`
	LockToken       string    `json:"LockToken"`
	MessageID       string    `json:"MessageId"`
}

My code is producing an error like the following when trying to unmarshal this:

failed to unmarshal servicebus metadata to ServiceBusMessageMetadata struct: parsing time ""\"2020-08-31T16:49:41.831Z\""" as ""2006-01-02T15:04:05Z07:00"": cannot parse "\"2020-08-31T16:49:41.831Z\""" as "2006"

I can validate this by running the following:

i := &InvokeRequest{
    Data: map[string]interface{}{
        "ContentType": "\"text/plain\"",
    },
}

fmt.Printf("I: %+v\n", i)

which produces:

I: &{Data:map[ContentType:"text/plain"] Metadata:map[]}

Notice that ContentType is surrounded in double quotes, exactly like how the InvokeRequest struct being handed to my function is.

Investigative information

Please provide the following:

• Timestamp: 2020-08-31 17:29:56.3769396 +0000 GMT
• Function App version: 3.0.14287.0
• Invocation ID: 03de2715-246f-42bf-b161-15a9ed879d9d
• Region: Central US

[ZachTB123]

@pragnagopa @anthonychu @yojagad

[ZachTB123]

A trigger such as timerTrigger does not have this issue:

^ image of what logging the InvokeRequest for a timer trigger looks like in Application Insights