Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question]: AzureRM modules in ADO agent,AzureRM should be retired #20809

Open
1 of 4 tasks
Alex-AZPS opened this issue Jan 28, 2025 · 2 comments
Open
1 of 4 tasks

[Question]: AzureRM modules in ADO agent,AzureRM should be retired #20809

Alex-AZPS opened this issue Jan 28, 2025 · 2 comments

Comments

@Alex-AZPS
Copy link

Task name

AzureRM modules are still widely used in ADO agent and should be retired

Task version

Azure PowerShell 6.X.0

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

Windows

Question

We learned from customer interviews that one branch uses an ADO agent (I assume this applies to all managed agents) that still has AzureRM modules.
Not only that, we have publicly announced that AzureRM is retired (https://learn.microsoft.com/en-us/powershell/azure/azurerm-retirement-overview?view=azps-13.1.0), these modules have reached the end of their useful life, and this situation may cause several issues, including security related issues.

We hope to work with Azure Devops to inform users that they can retire AzureRM.
@EshitaD
Copy link
Contributor

EshitaD commented Feb 4, 2025

Hi @Alex-AZPS, we are currently disabling FF for AzureRM modules, and it will be completed by the 12th of this month.

@mikebijl
Copy link

mikebijl commented Feb 6, 2025

I think we are running into issues because of this right now...

##[debug]Get Azure Endpoint
##[debug]USE_MSAL=true
##[debug]MSAL - USE_MSAL override is found: true
Wrapper Execution Failed: Cannot read properties of undefined (reading 'retrieveSecret')
Error Stack: TypeError: Cannot read properties of undefined (reading 'retrieveSecret')
    at Object.getEndpointAuthorizationScheme (/home/vsts/work/_tasks/*****/node_modules/azure-pipelines-tasks-azure-arm-rest/node_modules/azure-pipelines-task-lib/task.js:447:32)
    at AzureRMEndpoint.<anonymous> (/home/vsts/work/_tasks/*****/node_modules/azure-pipelines-tasks-azure-arm-rest/azure-arm-endpoint.js:52:45)
    at Generator.next (<anonymous>)
    at /home/vsts/work/_tasks/*****/node_modules/azure-pipelines-tasks-azure-arm-rest/azure-arm-endpoint.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/home/vsts/work/_tasks/*****/node_modules/azure-pipelines-tasks-azure-arm-rest/azure-arm-endpoint.js:4:12)
    at AzureRMEndpoint.getEndpoint (/home/vsts/work/_tasks/*****/node_modules/azure-pipelines-tasks-azure-arm-rest/azure-arm-endpoint.js:32:16)
    at /home/vsts/work/_tasks/*****/dist/wrapper.js:2:1490785
    at /home/vsts/work/_tasks/*****/dist/wrapper.js:2:1490824
Error Name: TypeError
Full Error: TypeError: Cannot read properties of undefined (reading 'retrieveSecret')

Can someone confirm that this is happening because of the decommision? If we hardcode the older version of the package:

  • "azure-pipelines-task-lib"
  • "azure-pipelines-tasks-azure-arm-rest"

it is still working. This looks like the ARM backend is still accepting "old" calls but now the package to get the secret of the service connection and authenticate to azure with it is not working anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants