-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Azure Identity SDK RC Test failed in Azure Cloudshell and Azure Webjobs #25810
Comments
This issue has been resolved with this PR #25829 and is released in the version 3.2.1. Can you please try this version of identity sdk and let me know if the tests pass for that? https://www.npmjs.com/package/@azure/identity |
@KarishmaGhiya Retest using version 3.2.1. In Azure Cloudshell, the test passed, but for Azure Webjobs, when test based on instruction (
|
please check if you are assigning the correct access policy and enable logging to see the whole error -
|
I am able to reproduce the issue, but not sure why this is happening. Will discuss with folks who originally worked on the test guidance and get back to you. Apparently, Java test also has the same failure. v-jiaodi |
The above issue has been moved to Azure/azure-sdk#902 (comment). |
Close this issue as it cannot be reproduced now. |
Describe the issue:
1.When test the Testing azure-identity in Azure Cloudshell with instruction for Test team(
Repro steps
) and run thenode index
command, it displays the error :2.When test the Testing azure-identity in Automate Azure Webjobs with instruction (
Repro steps
) and run theaz webapp webjob triggered run -w AzureTestJob -g $RESOURCE_GROUP -n $APP_NAME_SYSTEM_ASSIGNED
command, it displays the error :Environment:
Env: Azure Cloudshell and Azure Webjobs
package: @azure/identity@3.2.0-beta.2
Related issue: Azure/azure-sdk#795 and Azure/azure-sdk#902
Expected behavior:
Run the
node index
andaz webapp webjob triggered run -w AzureTestJob -g $RESOURCE_GROUP -n $APP_NAME_SYSTEM_ASSIGNED
expected to create secret successfully.@joshfree, @KarishmaGhiya, @mpodwysocki for notification.
The text was updated successfully, but these errors were encountered: