[BUG]: XML substitution output differs

[acdrivefurther]

New issue checklist

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

Task name

FileTransformV2

Task version

2.249.1

Issue Description

Using FileTransformV2 for XML variable substitution you get some similar output as below:

Processing substitution for xml node : connectionStrings
Processing substitution for xml node : appSettings
Updating value for key= SpaPath with token value: CONFIG_FILE_SETTINGS_TOKEN(SpaPath)

You can see individual keys that were updated within appSettings, one example above.

You don't get the same output when it's updating connectionStrings - it outputs that the section was processed, and they are processed fine but there is no output per key/value pair in devops.

Seems to be caused by these lines:

https://github.com/microsoft/azure-pipelines-tasks-common-packages/blob/a72c7dc7cc186b36c87139a951c5908c88173173/common-npm-packages/webdeployment-common/xmlvariablesubstitutionutility.ts#L267

https://github.com/microsoft/azure-pipelines-tasks-common-packages/blob/a72c7dc7cc186b36c87139a951c5908c88173173/common-npm-packages/webdeployment-common/xmlvariablesubstitutionutility.ts#L274

updateXmlConnectionStringsNodeAttribute is using tl.debug whereas updateXmlNodeAttribute is using console.log

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

Win11

Relevant log output

No error - just different output

Full task logs with system.debug enabled

No response

Repro steps

[EshitaD]

Hi @acdrivefurther, we have completed the deployments. Please verify and confirm.

[EshitaD]

Hi @acdrivefurther, we have completed the deployments. Please verify and confirm.

[acdrivefurther]

Hi @acdrivefurther, we have completed the deployments. Please verify and confirm.

Azure DevOps output is showing the additional detail now.

[EshitaD]

Hi @acdrivefurther, could you please share the exact log you are referring to?

[acdrivefurther]

The log output from the FileTransformV2 job when ran in Azure Devops, it's outputting the additional detail as expected now. All is good.

[EshitaD]

Thank you for the confirmation!! Closing this bug.