Section "Compile the custom handler for Azure" completely out of date

[MironAtHome]

[Enter feedback here]

---

Document Details

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

• ID: c524efc8-3aef-53b3-732b-6837d8f1c7a7
• Version Independent ID: a5d8005d-4431-a2b6-34bf-c463b76618c2
• Content: Create a function in Go or Rust using Visual Studio Code - Azure Functions
• Content Source: articles/azure-functions/create-first-function-vs-code-other.md
• Service: azure-functions
• GitHub Login: @ggailey777

• Microsoft Alias: glenga

  When following instructions on the page I have experienced the following issue. After deploying Azure Function for Rust, following documentation, I found the following warning message on one of the function app pages ( I didn't capture precise page and exact words ) Warning, change in azure, linux functions no longer supported on consumption plan.

  Please, update documentation accordingly and please do provide guidance how to deploy rust function. I would imaging with rust extending support to Windows OS there must be an option to deploy to Windows. However, the documentation does direct to use Linux OS for deployment. I am not sure what to make out of it on one hand. There is a second issue related to running such functions using time based trigger, cron expression. This one I am currently investigating, and at the moment, at least local hosting CLI framework, seems to be hard to configure to support such a binding for a custom handler, without running into a host of error messages that hardly make sense. In my understanding all that it takes to run cron expression based function is to

  1. provide such expression in function.json
  2. provide location of executable in function.json ( or some other config file )
  3. build executable and place it at the location specified
  4. ensure execution is guarded by appropriate function app policies with regard to duration and other infrastructure driven settings, on top of environment settings At the moment it appears there are at least two network ports and networking channels opened, one to storage hosting something ( not sure what, could be just storage for it's own sake ) the other one to logging channel, both of which apparently poorly documented and even worse documented is how to turn those off. In all the simplest and most ubiquitous ( this can be debated, but scheduled tasks in my experience is the most used azure function ) format, unless developer uses .NET, surrounded by just enough obstacles to make impression of somewhat less then fair effort from Azure team to support. It would be very nice to change this perception.

[mikeurnun]

Hello @MironAtHome - Thank you for your feedback! We will review and update as appropriate.

[PramodValavala-MSFT]

@MironAtHome Thanks for the feedback! We have assigned this issue to the content author to review and update accordingly.

The requirements for running Azure Functions with a Timer Trigger and Custom Handler are all required configuration with the way they are designed. The defaults are indeed fully packed for use cases that can best leverage bindings and other functionality that allow developers to focus on business logic and less on other aspects.

As for the network connection for storage, it is required by the timer trigger to hold a blob lease that is used to ensure only one instance is every running the schedule, especially when a function app scales out.

And for logging, Application Insights is the default and hence the connection. You could just remove the APPINSIGHTS_INSTRUMENTATIONKEY app setting. This would leave only file logging available which you can configure in host.json.