Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Azure Functions Runtime 2.0.12050-alpha breaking changes notice #129
Deployment of Azure Functions Runtime 2.0.12050-alpha has started. This release has significant breaking changes so please read the details below.
Please use Azure/app-service-announcements-discussions#64 for discussions related to this release.
If you are running on the Azure Functions 2.0 preview and don't want your app to break, you need to pin your Function App by following the instructions in the What can I do to avoid being impacted? section at the bottom of this announcement.
What is changing?
Extension model updates
Changes in bindings and extension model will impact your app:
Configuration settings changes
As part of configuration enhancements made to the runtime to allow for more flexibility, configuration settings names and the structure of
Function App secrets storage change
Function App secrets (function, system and master keys) will be stored in blob storage by default.
Previously they were stored in the file system and we are automatically migrating them to blob storage as part of this change, so keys should not change, but if you relied on direct file access or SCM APIs to manage those secrets, that will no longer work.
Single language functions in a Function App
Function App can only have functions of a selected language.
Previously a function app could have more than one language functions. We will now start enforcing a single language per app.
What do I need to do?
Choose a language for your Function App
Update your host.json file according to the updated schema located here.
Update your dependencies, extensions and/or code
If your function app is C#/F# based and developed locally (not through the portal) you'll need to update your NuGet reference for
Follow the instructions to update the extensions installed through portal
Read the Durable Functions release notes
If you use Durable Functions, read the release notes for the 1.6.0 release here.
Reference the Storage Extension where appropriate
If you have functions that work with Azure Storage (queue/tables/blob) either with triggers, input bindings or output bindings, you'll need to reference the new
Simplified WebHook URLs
WebHook URLs (like those used for EventGrid and Microsoft Graph) have been simplified.
I'm getting errors I dont understand, help!
There is a list of error messages with tips on how to resolve here.
What can I do to avoid being impacted?
To temporarily avoid impact, you can pin your Function App to the previous version of the runtime by updating the app setting
Version 2.0.11961-alpha will be available until the end of September 2018.
To pin your Azure Functions on Linux app, please update your image using the following mapping:
Using pinned version of core tools with Visual Studio
Visual studio keeps the core tools updated and in-sync with runtime version in Azure. You can override the default version of core tools launched by visual studio by performing the steps below.
One thing to note:
Publishing from Visual Studio to a pinned Function App
Added additional information about host.json above: