[BUG]: RuntimeStack parameter of AzureRmWebAppDeployment@5 has : instead of | (like v4) and it is silently failing

[steved0x]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

AzureRmWebAppDeployment

Task version

5

Issue Description

See https://dev.azure.com/msft-skilling/Content/_workitems/edit/401737

Basically, the list of values for the RuntimeStack parameter has changed from using | to using :

v5:

azure-pipelines-tasks/Tasks/AzureRmWebAppDeploymentV5/task.json

Line 231 in 649e9ca

"DOTNETCORE:9.0": ".NET 9.0",

v4

azure-pipelines-tasks/Tasks/AzureRmWebAppDeploymentV4/task.json

Line 237 in 649e9ca

"DOTNET|2.2": "DOTNET|2.2 (functionapp v2)",

The Runtime stack value is not being picked up by App Service config settings whenever deploying from Azure DevOps to the App Service deployment slot when utilizing AzureRmWebAppDeployment@5 and the RuntimeStack input utilizes a colon rather than a pipe.

See the linked issue above (or contact me on email, I don't want to post the private details here)

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Ubuntu

Relevant log output

See linked work item

Full task logs with system.debug enabled

 [REPLACE THIS WITH YOUR INFORMATION] 

Repro steps

[v-schhabra]

Hi @steved0x
Thanks for reporting this issue. We are investigating on it.
As a workaround you can type the value in the field "runtime stack"

[mbaric1]

Same issue for Node stack.

Passes stack value as NODE:20-lts instead of NODE|20-lts which makes whole App Service to fallback to PHP stack.