You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After experiencing the AzureRmWebAppDeployment@4 task being broken at least twice, we decided to lock it in our YAML pipelines to version 4.225.1. Due to the Node 10 deprecation warning, we are now attempting to update to the latest version.
We have found that when using the AdditionalArguments parameter and supplying MSDeploy arguments of form -setParam:name='X',value='Y' we are experiencing a bug. This appears to be logic that was introduced in 88ec513 related to encoding.
The change in behaviour has connection strings that were previously correctly encoded as:
New issue checklist
Task name
AzureRmWebAppDeployment
Task version
4.247.1
Issue Description
After experiencing the
AzureRmWebAppDeployment@4
task being broken at least twice, we decided to lock it in our YAML pipelines to version 4.225.1. Due to the Node 10 deprecation warning, we are now attempting to update to the latest version.We have found that when using the
AdditionalArguments
parameter and supplying MSDeploy arguments of form-setParam:name='X',value='Y'
we are experiencing a bug. This appears to be logic that was introduced in 88ec513 related to encoding.The change in behaviour has connection strings that were previously correctly encoded as:
To now be incorrectly encoded as:
Please note the following breaking changes:
"
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
windows-2022
Relevant log output
Full task logs with system.debug enabled
N/A
Repro steps
The text was updated successfully, but these errors were encountered: