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

Set your V1 Function Apps to ~1 #135

Open
paulbatum opened this Issue Sep 19, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@paulbatum
Member

paulbatum commented Sep 19, 2018

We have identified that a subset of customers have incorrectly configured V1 Function Apps. User action is required to configure these applications correctly to avoid potential impact. In the coming days this will start redirecting to ~2 which will break the large majority of apps with this setting.

Function Apps use the FUNCTIONS_EXTENSION_VERSION app setting to control which version of functions the app runs on. A V1 Function App should have this setting set to ~1. It should look like this:

image

and this:

image

Take Action

If you have a V1 app and you don't have this setting, fix it. Make sure it is set to ~1. Don't use values such as "latest" or "" (i.e. empty string).

If you have an automated deployment of any kind, make sure that your automated deployment is setting this correctly. We've seen cases where ARM templates are being executed that are missing this setting.

Also if you have a V2 app, you should set it to ~2 instead of "beta". That will prevent your V2 app from running into similar issues in the future.

Questions?

Please use Azure/app-service-announcements-discussions#69 for discussion of this announcement.

@Azure Azure locked and limited conversation to collaborators Sep 19, 2018

@davidebbo

This comment has been minimized.

Show comment
Hide comment
@davidebbo

davidebbo Sep 20, 2018

Contributor

Note that this is a continuation of this announcement from August 2017: #34. So this one is a reminder, as we're now about to release 2.0.

Contributor

davidebbo commented Sep 20, 2018

Note that this is a continuation of this announcement from August 2017: #34. So this one is a reminder, as we're now about to release 2.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.