-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Identity] [Hotfix] 1.4.0 increased the IMDS MSI default timeout #16055
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
Changes from all commits
5260452
9c287b3
0c49e9d
83b727c
70a8dcf
89b5d42
72a3bfc
254eec3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| { | ||
| "name": "@azure/identity", | ||
| "sdk-type": "client", | ||
| "version": "1.3.0", | ||
| "version": "1.4.0", | ||
| "description": "Provides credential implementations for Azure SDK libraries that can authenticate with Azure Active Directory", | ||
| "main": "dist/index.js", | ||
| "module": "dist-esm/src/index.js", | ||
|
|
@@ -55,7 +55,7 @@ | |
| "LICENSE" | ||
| ], | ||
| "engines": { | ||
| "node": ">=8.0.0" | ||
| "node": ">=12.0.0" | ||
| }, | ||
| "repository": "github:Azure/azure-sdk-for-js", | ||
| "keywords": [ | ||
|
|
@@ -74,14 +74,11 @@ | |
| "bugs": { | ||
| "url": "https://github.com/Azure/azure-sdk-for-js/issues" | ||
| }, | ||
| "engine": { | ||
| "node": ">=8.0.0" | ||
| }, | ||
| "homepage": "https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/identity/identity/README.md", | ||
| "sideEffects": false, | ||
| "dependencies": { | ||
| "@azure/core-http": "^1.2.4", | ||
| "@azure/core-tracing": "1.0.0-preview.11", | ||
| "@azure/core-http": "^2.0.0", | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you have to update the version of core-http? Seems like an unnecessary risk for a hotfix unless we have to take it
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think its because he needs the fix in #15906
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. On that note, should this hotfix branch take the update to core-tracing as well?
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nah, we can do that when core-tracing goes GA.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I still don't think this is the right thing to do. I worry about surprising someone with a whole host of changes unintentionally especially a major version change in core-http. Instead (and I know it's more painful, so sorry!), I would recommend releasing a hotfix to core-http with just the fix you need, then using that as the core-http version to release the hotfix to identity
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. After investigating about the new types, doing some simple tests and discussing this with @chradek , it seems safe for us to upgrade to core-http 2.0.0 on this Identity release.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The reason I believe it is safe is because
@maorleger is there anything in particular that worries you? Any testing we could do to assuage your concerns?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm fine with going to 1.4.0 with this, but was concerned when going to 1.3.1 👍 thanks for verifying the changes are safe |
||
| "@azure/core-tracing": "1.0.0-preview.12", | ||
| "@azure/logger": "^1.0.0", | ||
| "@azure/msal-node": "1.0.0-beta.6", | ||
| "@types/stoppable": "^1.1.0", | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -126,7 +126,10 @@ export class IdentityClient extends ServiceClient implements INetworkModule { | |
| `IdentityClient: refreshing access token with client ID: ${clientId}, scopes: ${scopes} started` | ||
| ); | ||
|
|
||
| const { span, updatedOptions: newOptions } = createSpan("IdentityClient-refreshAccessToken", options); | ||
| const { span, updatedOptions: newOptions } = createSpan( | ||
| "IdentityClient-refreshAccessToken", | ||
| options | ||
| ); | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I ran rushx format and it changed a bunch of files. I rather have these formatting changes than not have them. It will make it easier to do further hotfixes if necessary. |
||
|
|
||
| const refreshParams = { | ||
| grant_type: "refresh_token", | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.