Our great sponsors
-
app-service-announcements-discussions
Discussions for announcements from https://github.com/Azure/app-service-announcements/
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
azure-functions-nodejs-worker
The Node.js worker for the Azure Functions runtime - https://functions.azure.com
-
azure-functions-set-nodejs-version
Test lab consisting of 4 function apps to test switching of Node.js version in Azure Functions
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Note FUNCTIONS_EXTENSION_VERSION application setting (e.g. ~3) is not a reliable indicator. There was a platform upgrade for Azure Functions v2, where this app setting could remain at ~2 while in reality the runtime became 3.x. Confusing, I know.
On Linux, WEBSITE_NODE_DEFAULT_VERSION has no effect. It is the linuxFxVersion config option on the function app resource that defines the Node.js version. Note there's a bug where linuxFxVersion may be reported as empty in Azure CLI.
You can provide a full (Microsoft managed) Docker image name if you want to explicitly set the Azure Functions runtime version. Full list of supported Azure functions Docker tags can be found here. But you can also simply use node| as a shorthand. In this case, latest runtime version will be used. More on setting LinuxFxVersion here.
You can find sources for my test lab consisting of 4 function apps in the repo.