Using Azure Portal
~0.4 to ~0.5~0.5)Migrated and brand new Azure Functions should have similar Application Settings
Migrated and brand new Azure Functions (both on ~0.5runtime) have different Application Settings
Migrated (from ~0.4 to ~0.5) have WEBSITE_NODE_DEFAULT_VERSION set to 6.4.0
AzureWebJobsDashboard => DefaultEndpointsProtocol=https;AccountName=XXX;AccountKey=XXX
AzureWebJobsStorage => DefaultEndpointsProtocol=https;AccountName=XXX;AccountKey=XXX
FUNCTIONS_EXTENSION_VERSION => ~0.5
AZUREJOBS_EXTENSION_VERSION => beta
WEBSITE_CONTENTAZUREFILECONNECTIONSTRING => DefaultEndpointsProtocol=https;AccountName=XXX;AccountKey=XXX
WEBSITE_CONTENTSHARE => XXX
WEBSITE_NODE_DEFAULT_VERSION => 6.4.0
Brand new (~0.5) have WEBSITE_NODE_DEFAULT_VERSION set to 4.1.2
AzureWebJobsDashboard => DefaultEndpointsProtocol=https;AccountName=XXX;AccountKey=XXX
AzureWebJobsStorage => DefaultEndpointsProtocol=https;AccountName=XXX;AccountKey=XXX
FUNCTIONS_EXTENSION_VERSION => ~0.5
AZUREJOBS_EXTENSION_VERSION => beta
WEBSITE_NODE_DEFAULT_VERSION => 4.1.2
The application is still working with WEBSITE_NODE_DEFAULT_VERSION set to 4.1.2 but I'm a bit confused.. what is this setting? Why is it set to 4.1.2? Should I change it?
Provide any related information
This is likely a bug in our portal. We'll update this when we have the right Node.js version on the box.
Confirmed fixed in prod.