serverless-azure-functions icon indicating copy to clipboard operation
serverless-azure-functions copied to clipboard

Add support for Azure Functions v4

Open sathishmohan-ps opened this issue 2 years ago • 12 comments

This is a Feature Proposal

Description

Microsoft team launched Azure Functions 4.0 (GA) across Windows and Linux back in November, 2021. Could you please add support for latest version. serverless-azure-functions plugin allows us to deploy azure functions v3.5.2. We couldn't able to move to the latest version.

sathishmohan-ps avatar Apr 08 '22 09:04 sathishmohan-ps

What would be required to implement this and add support for .NET 6?

marcelvandesteeg avatar Jun 22 '22 05:06 marcelvandesteeg

I would also like to see this.

VictorioBerra avatar Jul 19 '22 23:07 VictorioBerra

Waiting on this one too.

mwesigab avatar Aug 17 '22 18:08 mwesigab

Following - we're wanting to use v4 as well for Node 16 support.

gligorkot avatar Aug 23 '22 01:08 gligorkot

Azure is ending support for Node12 soon, but using serverless-azure-functions we cannot upgrade our project to Node16. Is anyone working on this?

stefan-h-singer avatar Sep 30 '22 06:09 stefan-h-singer

Hello folks, I’ve recently got access to this project and in the coming weeks I will try to investigate this issue (among a few other open initiatives). If you have any insights about this particular feature, please share it, it will be much appreciated 🙇

pgrzesik avatar Oct 13 '22 23:10 pgrzesik

@stefan-h-singer it's a pretty easy thing to change. There is a pull request for nodejs14 that will get you a start.

kevin-boutin avatar Oct 18 '22 07:10 kevin-boutin

Hello folks 👋 I started digging a bit and it seems like it's possible to use v4 even in the current version. It looks like it's not documented though 😓 You can do so by setting functionApp.extensionVersion on provider like this:

provider:
  name: azure
  functionApp:
    extensionVersion: '~4'

It worked without issues for me, but you might want to first test it out on non-prod environment. In the next major version of the plugin it should be set to ~4 by default.

pgrzesik avatar Oct 23 '22 14:10 pgrzesik

Hello folks 👋 I started digging a bit and it seems like it's possible to use v4 even in the current version. It looks like it's not documented though 😓 You can do so by setting functionApp.extensionVersion on provider like this:

provider:
  name: azure
  functionApp:
    extensionVersion: '~4'

It worked without issues for me, but you might want to first test it out on non-prod environment. In the next major version of the plugin it should be set to ~4 by default.

I can confirm this does work. I've been doing this for months now.

kevin-boutin avatar Oct 24 '22 13:10 kevin-boutin