Feedback - Bad Choice for example Trigger

[Waiver-Wire-Addict]

[Enter feedback here] So, the HTTP Trigger being the simplest trigger is a bad choice. The ONLY time the HTTP trigger consumes/interacts with OTHER Azure resources when you deploy the function, which I might do until I am going to prod with Local Dev--Azure costs money. You don't have a clear how-to on a Trigger like a Blob Storage trigger that in addition to its code has Azure configuration that is needed. This is Azure Functions, why not show Azure interaction. It's easier to go from a Blob Trigger example to an Http Trigger, than the reverse. Anyway frustrated with the Blob Trigger and Azure Functions examples in general, because they are so Http Trigger oriented, and don't help at all when you have to work with the more complex Trigger types. If you don't want to do a simple how-to for each trigger type, then why not a Best Practices -- For Dev and Prod for each of the Trigger types. You know, like here is where you should store your Blob connection secret in Prod, and make sure .gitignore the local setting file in Dev, but organized by trigger type, since each flavour (Canadian) has its own unique set of configuration parameters.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 542c2bdc-5868-71d5-1d1a-a2c6d61744b0
• Version Independent ID: 1bba15a0-227a-8137-a023-90b8df19881b
• Content: Create a Python function using Visual Studio Code - Azure Functions
• Content Source: articles/azure-functions/create-first-function-vs-code-python.md
• Service: azure-functions
• GitHub Login: @ggailey777
• Microsoft Alias: glenga

[Naveenommi-MSFT]

@Waiver-Wire-Addict Thanks for your feedback! We will investigate and update as appropriate.

[MughundhanRaveendran-MSFT]

@Waiver-Wire-Addict , Thanks for your feedback. I will pass on this message to the content team to add addtional trigger examples in the python documentation. Please note that we have seperate section for different triggers and bindings.

[MughundhanRaveendran-MSFT]

@Waiver-Wire-Addict , If you dont have any other queries or concerns, I will close this issue for now. As I mentioned, I will pass on the feedback. Thanks

[Waiver-Wire-Addict]

Yes, I had read that documentation before submitting my feedback. That documentation is like an API reference. It does not document how one would use the triggers, or how one might debug the triggers. It just documents that the trigger types exist. That is why I submitted my feedback on the "Example Trigger" page, which does attempt to show how one would use the triggers, and how one would code/debug them. If the documentation you referred me to was at all informative, I would not made my feedback. I am still trying to figure out how to locally debug a blob azure trigger. There is nothing in either the quick start example, or the azure blob triggers that explains how one might do that. That is why the HTTP trigger is a bad example. I can't figure out how to debug an Azure Blob Trigger locally from the HTTP trigger example because the contexts are so different. I mean maybe you can't debug the Azure Blob Trigger locally, but the Quick Start example CERTAINLY leaves you with the impression that you can debug all the triggers locally.

On Wed, Nov 30, 2022 at 11:57 PM Mughundhan_R-MSFT @.***> wrote:

@Waiver-Wire-Addict https://github.com/Waiver-Wire-Addict , Thanks for your feedback. I will pass on this message to the content team to add addtional trigger examples in the python documentation. Please note that we have seperate section for different triggers and bindings.

[image: image] https://user-images.githubusercontent.com/56299140/204968971-76a237c6-4c70-4ad9-9390-4f15440fce8f.png

— Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/azure-docs/issues/102048#issuecomment-1333170650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH3LG2HVXJ5G7GRPMC4CFFDWLAV2XANCNFSM6AAAAAASOSSZG4 . You are receiving this because you were mentioned.Message ID: @.***>

[MughundhanRaveendran-MSFT]

@Waiver-Wire-Addict , Yes, as you mentioned, input context differs for each trigger. If you are facing any trouble with the blob trigger function, you can post a query in Q&A forum. In fact, you can debug all triggers locally. https://learn.microsoft.com/en-us/azure/azure-functions/functions-develop-local