Open gabrielweyerjb opened 1 year ago
@manolerazvan can you help with someone to look into this?
Also seeing this. Not sure what issues it is causing but a deploy last week did not show the warning.
Hello,
I'll follow up more on this tomorrow. The Task Lib supports adding resource paths via https://github.com/microsoft/azure-pipelines-task-lib/blob/ab676de8207ae472532e84765d3c9c5e290cb85b/node/internal.ts#L147
This takes a path and an optional parameter to ignore warnings. If this is true then this is this is logged as a Debug statement otherwise it is logged as a warning. The default is false.
The Azure Function App Task always has called this function with just the path name and not the optional parameter.
tl.setResourcePath(path.join( dirname, 'task.json')); tl.setResourcePath(path.join( dirname, 'node_modules/azure-pipelines-tasks-azure-arm-rest-v2/module.json'));
Will discuss with the library team to check what's happening here.
This issue has been addressed in this PR https://github.com/microsoft/azure-pipelines-tasks/pull/18592
This should be resolved in 2.225. Closing this issue
Confirmed as fixed in 2.225.1
which has started rolling out.
Seems like this problem pops up again with agent version 243.1. :-(
Thanks, let me check into this.
I have the same on 2.245.1
I think this is related to https://github.com/microsoft/azure-pipelines-tasks/issues/20408
Task name
AzureFunctionApp
Task version
2.223.1
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
Microsoft Windows Server 2019
Task log
Relevant log output
Aditional info