Storage Queue Message, allow us to supply a messageId on add

[MrAntix]

Library name

Azure.Storage.Queues 12.23.0

Please describe the feature.

I would like to be able to supply an id for a message rather than have the system generated one.

This would mean we could "upsert" into the queue allowing debounce mechanisms with the existing visibility timeouts

Right now, I have to add a new message every time, which means my trigger gets hit by every message which means unnecessary compute and cost. If I could upsert with my id, then there would only be one message delivered for that messageId.

As I understand it, the messageId is a GUID anyway, does that mean this would be possible to do?

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @amnguye @jalauzon-msft @jaschrep-msft @nickliu-msft @seanmcc-msft.

[MrAntix]

From the API docs, there are two relevant endpoints

1. Insert Put Message https://learn.microsoft.com/en-gb/rest/api/storageservices/put-message#request
   Does not contain the message id in the route

2. Update Update Message https://learn.microsoft.com/en-gb/rest/api/storageservices/update-message#request
   Does contain the message id in the route

so, you could have an Upsert Message POST with the message id in the route

this would be a new route, so would not break existing valid calls to the Put/Update Message

Insert    [POST] {queue}/messages
Update    [PUT] {queue}/messages/messageId
Upsert    [POST] {queue}/messages/messageId

[MrAntix]

Currently we can schedule messages in Storage Queues, but we then have to store the id generated if we need to update, which is another operation.

If we could supply the id, we could tie it to data that already exists, meaning a second operation is not need.

This would allow for more resiliient design

[amnguye]

Hi thanks for submitting this issue! It sounds like you're asking for a new REST API for the Queues Storage Service, and actually not specifically related to the .NET Storage SDK (since the Storage SDK works on top of the REST API).

I recommend submitting this feature request to
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request