Open sijucm opened 3 years ago
@sijucm Thanks for your feedback! We will investigate and update as appropriate.
@sijucm sorry for the trouble you've had using our documentation for Azure Functions. Since the link you provided was a bit odd, can I get you to confirm that this is the article that you found unhelpful: Azure Blob storage input binding for Azure Functions - Example?
Assuming so, I think we have two issues here:
I am going to #reassign:@craigshoemaker who owns this article to see if we can improve the example to something less trivial. In the meantime, providing an example of what you were wanting to see would be helpful.
Thanks again very much for your helpful feedback!
Thanks for the response. The page mentioned is correct, I just found the github page that is publishing this. What I searched for is : "Azure functions javascript blob storage input binding data". I cannot find any reference to what comes as the input data to the function. What Object and what are the attributes I can use. I see this page but this does not connect to any advanced reference on the API/documentation.
In the published page located at: https://github.com/msangapu/azure-docs-PUBLIC/blob/master/articles/azure-functions/functions-bindings-storage-blob.md#input---javascript-example
It shows example of a blob storage input trigger as given : context.bindings.myOutputBlob = context.bindings.myInputBlob;
That's so easy to do without carefully not giving any information for the reader on what is in the myOutputBlob for example if I want to process that data instead of copying it into a different container. Very typical of MS to give correct information but useless information. Please, please give some information on what comes in the context.bindings.myOutputBlob or where I can find further documentation/reference. I'm searching desperately but seems like the google-search lead me again and again to this documentation itself.
I'm sorry for the emotions in this post, but it comes out of deep frustration working with MS products. The amount of inconsistencies, lack of any useful documentation, half baked products, rabbit holes of what works with complex permutations and combinations.