azure-pipelines-tasks: Warnings about Resource file already set when using AzureKeyVault v1.212.0

Hi all, Quick update: Azure KV version 213 (both task and variable group) which fixes the warning issue, has been rolled out to south Brazil and EUS2 region for now. There is a slight delay, but version 213 will be rolled out to all regions and users by end of December 1st week.

Starting with version 1.213.0, this warning is showing up in the PipAuthenticate@1 task. The task seems to be working correctly aside from the warning. Previously, we were using version 1.206.0.

https://github.com/microsoft/azure-pipelines-tasks/pull/17151 revert is completed, will take time to roll out 213

We’re using Azure DevOps and Hosted Agents and we’re not directly referencing this task in our pipelines, but we are using variable groups, defined based on Azure KeyVault, which probably causes implicit use of this task (it shows up in the log, with version 1.212.0). This basically translates to all of our pipelines being affected by this issue, with no way to address it, without remaking all our pipelines to explicitly use the task in a corrected version.

The agent is running version 2.213.2, and started with a clean set of agents and we are still getting the message:

Resource file has already set to: /azp/agent/_work/_tasks/AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e/1.212.0/node_modules/azure-pipelines-tasks-azure-arm-rest-v2/module.json

Seems like it is still an issue:

apologies, version 2.225.0 will contain the fix. Here is the PR https://github.com/microsoft/azure-pipelines-tasks/pull/18592.

@fvilches17 version 1.225.1 will contain the fix.

We’re seeing it in AzureAppServiceSettings tasks every time that they run. Version: 1.223.0

Looking at old logs, I doesn’t look like it was happening in 1.215.0, but it was happening in 1.221.102

Can someone confirm if this is addressed and where (which tasks) have this addressed? Companies are paying a crap ton of money for MSDN subscriptions/licenses, which cover the Azure DevOps, plus another crap ton of money for additional services on Azure DevOps (like hosted agents) and we can’t even get an update on if an issue is resolved or not. Do we need to pay for that separately? Is it like with Apple products, that you have to pay for each and every feature separately?

With version 213 the warning is gone on our side.

@v-mohithgc can you please share the status of the rollout? namely when the new version is expected to land on msazure?

We are also running into this issue. Any resolution so far? It is for our download secrets task from a variable group that is linked to an azure key vault.

We’ve got AzureKeyVault auto updated to v1.212.0 on a lot of our self-hosted server agents. Is there any easy way to revert all those to v1.211.2?

Hi, you can try to clean agent tasks cache.

Example path: {agentname}\ _work \ _tasks *

I already tried that and it does not help, these warnings appear immediatly with the first run after cleaning.

Task version has been rolled back to 1.211.2

+1 Our team started seeing this issue on October 31st with version 1.212.0. The previous version, 1.211.2 did not have this issue. Is there any plan to update to a new version with a fix, or something we can do on our end to resolve the warnings?

+1 . We are facing issues with the same. We are seeing multiple warnings while fetching secrets from Azure Key vault using the task

• task: AzureKeyVault@1

Error

##[warning]Resource file has already set to: /azp/agent/_work/_tasks/AzureKeyVault_1e244d32-2dd4-4165-96fb-b7441ca9331e/1.212.0/node_modules/azure-pipelines-tasks-azure-arm-rest-v2/module.json