keesschollaart81 / vsts-arm-outputs

Azure DevOps Pipelines Extension - Use your ARM Deployment outputs
https://marketplace.visualstudio.com/items?itemName=keesschollaart.arm-outputs
MIT License
28 stars 14 forks source link

Unhandled exception during ARM Outputs Task Error: secret must be a non empty string #384

Open sukdev157 opened 8 months ago

sukdev157 commented 8 months ago

Starting: ARM Outputs

Task : ARM Outputs Description : This task reads the output values of an ARM deployment and sets them as Azure Pipelines variables. Version : 6.0.0 Author : Kees Schollaart Help : More Information

Logging in using ApplicationTokenCredentials, authScheme is 'WorkloadIdentityFederation' Unhandled exception during ARM Outputs Task Error: secret must be a non empty string. at new ApplicationTokenCredentials (webpack://arm-outputs/./node_modules/ms-rest-azure/lib/credentials/applicationTokenCredentials.js?:83:13) at AzureDevOpsArmOutputsTaskHost.getCredentials (webpack://arm-outputs/./dist/index.js?:100:31) at AzureDevOpsArmOutputsTaskHost.eval (webpack://arm-outputs/./dist/index.js?:33:40) at next (native) at eval (webpack://arm-outputs/./dist/index.js?:8:71) at awaiter (webpack://arm-outputs/./dist/index.js?:4:12) at AzureDevOpsArmOutputsTaskHost.run (webpack://arm-outputs/./dist/index.js?:20:26) at eval (webpack://arm-outputs/./dist/index.js?:118:31) at Object../dist/index.js (C:\Azure\SHP_work_tasks\ARM Outputs_584bcff2-3353-4f11-872b-6ba01267a972\6.0.0\index.js:131:1) at __webpack_require (C:\Azure\SHP_work_tasks\ARM Outputs_584bcff2-3353-4f11-872b-6ba01267a972\6.0.0\index.js:30:30)

[error]Error: secret must be a non empty string.

Finishing: ARM Outputs

andrewholler commented 8 months ago

Same as #383

pcoetzer-hyrdeiot commented 8 months ago

I get the feeling this project is not being maintained anymore as it was last updated what 3 years ago. A pity...

StefanoUrsino commented 8 months ago

Hi,

we are experiencing the same error.

image

@keesschollaart81 Is there any chance that this will be fixed?

I tried with both versions 5.X and 6.X

BennyM commented 3 months ago

You can fix it by removing the task from your pipeline and use the approach as illustrated in this article: https://ochzhen.com/blog/parse-arm-template-outputs-in-azure-pipelines