Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Functions Runtime 2.0 Preview Breaking Change Notice #106

Closed
fabiocav opened this issue May 10, 2018 · 2 comments
Closed

Azure Functions Runtime 2.0 Preview Breaking Change Notice #106

fabiocav opened this issue May 10, 2018 · 2 comments

Comments

@fabiocav
Copy link
Member

fabiocav commented May 10, 2018

A new version of the Azure Functions Runtime 2.0, is being prepared.

This is notice is being posted in advance to prepare users running on the current Azure Functions 2.0 preview version for the following potential breaking changes:

NOTE: Some of the changes listed here are from the previous release, since that deployment was aborted.

  • Java Language Worker: For customers with existing Java functions, that were deployed using Maven Plugin version 0.2.1 or any other earlier versions will be affected as the deployment includes package azure-functions-java-core 1.0.0-beta-2 that is incompatible with the current functions runtime. An update to maven plugin will be published soon. Until then please follow workarounds mentioned below to avoid downtime:
    During the deployment please pin functions runtime version to 2.0.11651-alpha
    To use the latest runtime, please delete azure-functions-java-core-1.0.0-beta-2.jar from the lib folder
    Please note that azure-functions-java-core-1.0.0-beta-2.jar needs to be deleted from the lib folder for new Java functions as well until we release updated maven plugin

  • Assembly resolution/binding behavior changes: Assembly resolution/binding behavior has been changed, which may impact existing applications relying on previous binding behavior and using custom resolution patterns (e.g. subscribing to AppDomain AssemblyResolve event).

  • Blob poison message handling: Blobs.CentralizedPoisonQueue default changed (details)

  • Console logging configuration: Environment name changed to consoleLoggingMode (details)

What can I do to avoid being impacted?

To avoid impact, you can pin your Function App to the current version of the runtime now by updating the app setting FUNCTIONS_EXTENSION_VERSION to 2.0.11651-alpha. Once the new version is released, you will not be automatically upgraded and will have the ability to test your code with the new version, which we recommend you do in a different Function App.
This version will remain available until June 13th.

Please use Azure/app-service-announcements-discussions#46 for discussions related to this release.

@fabiocav
Copy link
Member Author

Deployment of runtime version 2.0.11776 has started. If you have any issues, please use Azure/app-service-announcements-discussions#46 for discussion.

@fabiocav
Copy link
Member Author

This runtime deployment has been completed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant