question

stevemrf-4055 avatar image
0 Votes"
stevemrf-4055 asked stevemrf-4055 edited

Storage Queue Node SDK. Unexpected sendMessage response.

Hi Folks,

Using the sdk (@azure/storage-queue) is straightforward and I'm able to create, read and delete messages in a storage queue via an Azure static web app API function written in javascript.

The response I'm getting when adding a message to a queue is very verbose, around 56k, and includes details like the account shared key and extensive account and queue metadata. It is not the response detailed in the put-message docs.

This may be expected behaviour, I'm fairly new to azure queues so although I can code for it there's gaps in my knowledge and I haven't been able to find anything that explains a response of this nature. Would there be an option I can set to request a minimal response? That's a lot of data I'll never use. I only need an indication of success/failure.

If it isn't expected, I can send the responses. I would post now but I'm a bit nervous of posting without going over them carefully and removing any security data..


Thanks for any guidance you can offer, much appreciated.






azure-queue-storage
· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@stevemrf-4055 Apologies for the delay! I’m checking on this internally with the product team and will get back to you with something concrete.

0 Votes 0 ·
stevemrf-4055 avatar image stevemrf-4055 SumanthMarigowda-MSFT ·

Hi @Sumarigo-MSFT , thanks and no worries. I can post a response if you need it. I think I've removed the sensitive information.

0 Votes 0 ·

@stevemrf-4055 I wish to engage with you offline for a closer look and provide a quick and specialized assistance, please send an email with subject line “Attn:subm” to AzCommunity[at]Microsoft[dot]com referencing this thread and the Azure subscription ID with detailed information on the issue. I will follow-up with you. Once again, apologies for any inconvenience with this issue.
Thanks for your patience and co-operation.

0 Votes 0 ·
Show more comments
stevemrf-4055 avatar image
0 Votes"
stevemrf-4055 answered

So this is turning into a serious issue for me. Two weeks I've been looking for this info. It's a well established service, I'm surprised this is proving so difficult. This wasn't the first place I tried to find the information

All I want to know is, is the response expected? It's not documented, as far as I can see, and exposes shared keys to services, which is a concern.

If it is expected I can deal with it I just don't want to do extra work when there's no need as it means more services to manage. As nice as the Azure management tools are it's still a lot of extra work and expense.

P.S. Serious not sarcastic question - would I get an answer to this if I bought a support package? What would paid support do differently here that makes it worth having?



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

stevemrf-4055 avatar image
0 Votes"
stevemrf-4055 answered stevemrf-4055 edited

I'm still looking for a pointer to documentation that details the response I'm getting. The official put-message docs give no information regarding 56k of headers and metadata returned from a request, a far more concise response is given in docs & examples.

Any pointer appreciated, a link to a document if available would be brilliant.

Many thanks
Steve

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@stevemrf-4055
Sorry to hear you are still facing issues. We tried engaging with you privately, but were unsuccessful. We are unable to find the previous email you have sent. Please send an email with subject line“Attn:deherman” to AzCommunity[at]Microsoft[dot]com referencing this thread and the Azure subscription ID with detailed information on the issue. We will follow-up so you can work directly with an engineer.

0 Votes 0 ·

Hi :)

Thanks for getting back to me. I'm really sorry if I've missed emails. I'm surprised but it can happen. I'll send details to you now. Thanks for looking into this for me.

Cheers
Steve

Update: email sent, delivered at 22:49

0 Votes 0 ·