-
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
error when create a ApplicationInsightsManagementClient instance #10045
Comments
@changlong-liu Can you please take a look at this issue? Thanks |
FYI. Error messages are: 818 const appinsightsClient = new ApplicationInsightsManagementClient(tokenCredential, this.subId); ../../node_modules/@azure/arm-appinsights/node_modules/@azure/ms-rest-js/es/lib/httpHeaders.d.ts:24:22 src/botProjectDeploy.ts:853:54 - error TS2345: Argument of type 'import("/Composer/plugins/node_modules/@azure/ms-rest-js/es/lib/credentials/serviceClientCredentials").ServiceClientCredentials' is not assignable to parameter of type 'import("/Composer/plugins/node_modules/@azure/arm-appinsights/node_modules/@azure/ms-rest-js/es/lib/credentials/serviceClientCredentials").ServiceClientCredentials'. 853 const botServiceClient = new AzureBotService(tokenCredential, this.subId); Found 2 errors. |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azmonapplicationinsights. |
Hi applicationinsights service team, the JS SDK is using a old version of ms-rest, would you confirm we need to release a new SDK based on latest swagger? Thank you. |
@changlong-liu The last update to I would take that as an indication that the service team has been making the swagger updates assuming that the automation would take care of updating the packages. So, I would highly recommend updating the package and not only unblock the customer, but also allow them to use the new features. cc @tofriedl and @majastrz, the last two people to update the swagger for confirmation |
Hi @ramya-rao-a , thanks for comments. I'll involve you in the mail thread we discussing this with the issue submitter and ApplicationInsights service team. The reasons we didn't release new package by ourselves are:
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sgellock. |
Update for current status: |
@stevengum , Hi, could you please help submit a release request for bot service? |
@luhan2017 @VanyLaw @changlong-liu, sorry for the delay the release request has been filed. |
Hi @stevengum , @VanyLaw , the botservice JS package is available here: https://microsoft.sharepoint.com/:u:/t/AzureManagementExperience/EesAOwtz9LZPsOex0y0AI54BegRKJUFDa5Oz4zNPqiYQcQ?e=TDGtYM Would you verify it before public release? Thank you! |
Hi @changlong-liu , it can work in my site. Thanks! |
Hi @VanyLaw , the botservice is released here: https://www.npmjs.com/package/@azure/arm-botservice/v/2.0.0 |
Hi @VanyLaw , shall I know whether have any issue on the packages, shall we close this issue? |
Closing this issue as both the |
Describe the bug
I can not new a ApplicationInsightsManagementClient instance(come from @azure/arm-appinsights) and AzureBotService instance (come from @azure/arm-botservice) if I only have a accessToken.
I create a TokenCredentials instance with accessToken, which is implement the ServiceClientCredentials, and try to use this as the parameter to create ApplicationInsightsManagementClient and AzureBotService, but failed. I guess it's because the version of @azure/ms-rest-js package which is dependency in @azure/arm-appinsights and @azure/arm-botservice is out of dated.
Could anyone can update the dependency package version of @azure/arm-appinsights and @azure/arm-botservice? Or could you tell me how to create those two types of instances just by accessToken?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: