[REGRESSION]: Azure CLI@2 - toolExecutionError.indexOf is not a function about azure-pipelines-tasks

[shanoor]

Meanwhile, we can use the previous version of the task by using task: [email protected].

[LeftTwixWand]

Hello @ponbac, @JulianCodespotiMYOB and @jonmikeli
Thank you for reaching me.

As @ponbac noticed, my changes do not work properly. But the indexOf issue occurs in the error-handling part of the code.
Which means that the error has already happened.

The most common reason for service connection error - is expired secrets.
So please, check the secrets on your service connection are valid.
If not - please update the secrets or (recommended): convert your service connection from secrets-based to Workload Identity Federation. This should mitigate the issue for some of you.

From my side, I'll try to revert the changes asap.

[ChuckFinster]

Adding a note that I am using service connections with federated identity and recevied the same error. Using @shanoor's comment about downgrading the task version bypassed the error.

[chandlerkent]

Just wanted to note that we are also having this issue and we are also using Workload Identity Federation. Downgrading as suggested by @shanoor fixes the issue.

@LeftTwixWand

[jonmikeli]

Hello @ponbac, @JulianCodespotiMYOB and @jonmikeli Thank you for reaching me.

As @ponbac noticed, my changes do not work properly. But the indexOf issue occurs in the error-handling part of the code. Which means that the error has already happened.

The most common reason for service connection error - is expired secrets. So please, check the secrets on your service connection are valid. If not - please update the secrets or (recommended): convert your service connection from secrets-based to Workload Identity Federation. This should mitigate the issue for some of you.

From my side, I'll try to revert the changes asap.

Hi @LeftTwixWand ,

Thank you for your answer.
In case it helps, I have created a new connection and same result.

I will use the former version while the issue is solved.

[laplace-deploy]

Same problem here, even using Workload Identity Federation

[JulianCodespotiMYOB]

I had a similar issue occur, but for me it was due to not passing in an appropriate Azure Subscription. Perhaps this could be your issue? Maybe try confirming whether this subscription exists or not 🤔

[ponbac]

I had a similar issue occur, but for me it was due to not passing in an appropriate Azure Subscription. Perhaps this could be your issue? Maybe try confirming whether this subscription exists or not 🤔

Yes, the reason our pipeline is failing in the first place is due to something else, but this issue is about the error not getting properly logged because of the indexOf error crashing the task before the real error can get reported.

[jonmikeli]

Some issue for me with a service connection.

[iurietopor]

Faced the issue today. We are using Workload Identity Federation as well.

Edit:
Found the issue on our side. azureSubscription: '' under task inputs:.
We didn't apply the template with variables for new added job. The name of service connection is defined there.

Used this Google Chrome extension to see the final rendered YAML: ADO Pipeline Assistant

Relevant snippet from final rendered YAML:

    - task: AzureCLI@2
      displayName: Get WebApp Host-Name
      inputs:
        azureSubscription: ''
        scriptType: bash
        ....

[ajayadav7]

if you use task: [email protected] then you will get the error: 'unable to locate executable file: 'powershell'. Please verify.....

and this is the actual error.

to resolve this just add the pool image as 'windows-latest' and it will work with task: AzureCLI@2 also.

you need to add the below part in your script before the task

pool:
vmImage: "windows-latest"
steps:

• task: AzureCLI@2