[enhancement]: Please add support for AzureFunctionApp@2 to deploy .net 8 Isolated model

[hyndakiel]

Task name

No response

Describe your feature request here

Hello,
This is my first time creating a issue here on gihub so if I created in the wrong way please tell me.
Right now version 2 of AzureFunctionApp can only deploy up to .net 7 Isolated model, is there any idea when .net 8 will be supported?

Thank you for your time

[FinVamp1]

@hyndakiel Is this for deploying to a Linux Function App? If so I will be working on this and hope to have it out this month

[hyndakiel]

@FinVamp1 , yeah deploying on Linux Function App. In the meantime my workaround is to call azure CLI after the deploy with something like this
"az functionapp config set -g resource-group -n func-name --linux-fx-version '"DOTNET-ISOLATED|8.0"'".

Good to know that you are working on this soon.

[acha11]

Hi, @FinVamp1 any update on the ETA for this enhancement? That info would help us decide whether to temporarily apply manual changes to a couple of non-prod environments (if it's coming soon) or introduce azure CLI steps to our deployment as per @hyndakiel's solution above.

[FinVamp1]

Thanks, I'm also going to update the tool tip for this to indicate that this value is editable. So while DOTNET-ISOLATED|8.0 is not available yet you can just put it in right now and your app should deploy and work without any issues. @acha11 I was hoping to target this month but it will probably most likely be next month now.

[FinVamp1]

In the YAML It would look this this.

runtimeStack: 'DOTNET-ISOLATED|8.0'

Or in the assistant.

[ZarPeter]

UPDATE: Please ignore the below! Didn't read your second to last comment stating it will most likely be deployed next month.

___ prev comment ___

Hey Thank you for your hard work!

I tried updating our AzureFunctions to dotnet8 using yaml, but the runtime is not updated..
This is the relevant YAML section.

• task: AzureFunctionApp@2
  displayName: 'Deploy queue processor function'
  inputs:
  azureSubscription: ${{ parameters.azureServiceConnection }}
  appType: 'functionAppLinux'
  appName: ${{ parameters.functionsAppName }}
  runtimeStack: 'DOTNET-ISOLATED|8.0'
  deployToSlotOrASE: true
  slotName: 'staging'
  package: '${{ parameters.artifactsDirectory }}/api/Auditing.Functions.zip'
  ResourceGroupName: ${{ parameters.resourceGroupName }}

However in the deployment pipeline this is not reflected and the function runtime is not updated.

Can you help me with this please somehow?

kind regards,

Zar

[fjbelizon]

@FinVamp1 When will this functionality be implemented? DOTNET-ISOLATED 8.0 is active as of November 2023. Thank you in advance.

[FinVamp1]

Hello, this will be released soon in version 237 of both v1 and v2 Task.

[pacorreia]

Hi @FinVamp1

I saw this was released 4 hours ago, but how long until it's actually available for use?

For me I can't still set dotnet-isolated version 8 for linux Function apps:

[tomasr]

+1 from me.

Can't seem to get this to work at all. Publishing succeeds, but the linuxFxVersion of the function never gets updated and gets stuck in DOTNET|6.0

And the portal UI shows the runtime stack in an unusable state:

I have tried this in all possible combinations and I've just reached the conclusion this is completely broken. Obviously changing it from the UI fixes the broken function app, but that defeats the purpose of doing reliable upgrades through the DevOps pipeline.

[FinVamp1]

Hello, I filed an enhancement for this today #19866 . We don't update the linuxfxversion but just the app settings. I'll check to see if we can add this functionality. The flow is that you have an existing .NET 6 app that you have rewritten in .NET 8 and you want to deploy and update the App Version as well as the code?

[tomasr]

@FinVamp1 That is correct, that's the scenario. Too bad it's not supported, since that makes setting the runtimeStack pretty useless on its own. At least now I know I'm not going crazy :)

[FinVamp1]

I'll discuss this internally and see what we can do.

[Saulopv]

@tomasr You are not crazy :) I did the same thing, spending a lot of hours trying to make it work