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

Keep getting Error: domain must be a non empty string. when using V6 #375

Open
joshuamiller52 opened this issue Nov 7, 2022 · 3 comments

Comments

@joshuamiller52
Copy link

Z Logging in using ApplicationTokenCredentials, authScheme is 'ServicePrincipal'
2022-11-07T22:13:33.2603615Z Unhandled exception during ARM Outputs Task Error: domain must be a non empty string.
2022-11-07T22:13:33.2604727Z at new ApplicationTokenCredentials (webpack://arm-outputs/./node_modules/ms-rest-azure/lib/credentials/applicationTokenCredentials.js?:79:13)
2022-11-07T22:13:33.2605956Z at AzureDevOpsArmOutputsTaskHost.getCredentials (webpack://arm-outputs/./dist/index.js?:100:31)
2022-11-07T22:13:33.2606864Z at AzureDevOpsArmOutputsTaskHost.eval (webpack://arm-outputs/./dist/index.js?:33:40)
2022-11-07T22:13:33.2607574Z at next (native)
2022-11-07T22:13:33.2608183Z at eval (webpack://arm-outputs/./dist/index.js?:8:71)
2022-11-07T22:13:33.2608983Z at __awaiter (webpack://arm-outputs/./dist/index.js?:4:12)
2022-11-07T22:13:33.2609782Z at AzureDevOpsArmOutputsTaskHost.run (webpack://arm-outputs/./dist/index.js?:20:26)
2022-11-07T22:13:33.2610594Z at eval (webpack://arm-outputs/./dist/index.js?:118:31)
2022-11-07T22:13:33.2611505Z at Object../dist/index.js (C:\B17-2_work_tasks\ARM Outputs_584bcff2-3353-4f11-872b-6ba01267a972\6.0.0\index.js:131:1)
2022-11-07T22:13:33.2612586Z at webpack_require (C:\B17-2_work_tasks\ARM Outputs_584bcff2-3353-4f11-872b-6ba01267a972\6.0.0\index.js:30:30)
2022-11-07T22:13:33.2807701Z ##[error]Error: domain must be a non empty string.

@Tosters
Copy link

Tosters commented Jun 15, 2023

Having the same issue.

@tudoranghelina91
Copy link

I have it too

@Ashherr1
Copy link

To anyone else experiencing this issue a simple fix is to use a manual service connection.

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

No branches or pull requests

4 participants