-
Notifications
You must be signed in to change notification settings - Fork 13
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
chore: upgrade az identity in keyvault secret provider #432
base: main
Are you sure you want to change the base?
chore: upgrade az identity in keyvault secret provider #432
Conversation
✅ Deploy Preview for arcus-security canceled.
|
@@ -24,7 +24,7 @@ | |||
</ItemGroup> | |||
|
|||
<ItemGroup> | |||
<PackageReference Include="Azure.Identity" Version="1.10.2" /> | |||
<PackageReference Include="Azure.Identity" Version="1.11.0" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering, why not the latest version (if this is not the latest version - which I assume because of the PR description).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.11.3 is the latest version it seems:
https://github.com/Azure/azure-sdk-for-net/releases/tag/Azure.Identity_1.11.3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but choose the 'minimum latest' as to not force the version upon people. We did this previously, too, so we are more broadly supported.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The latest version is a patch that contains some bugfixes .... I dont see a problem in using that latest version here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's more a library dev idea than a product dev idea. As in that we try to use the best yet lowest supported package. Since we recently released a major version, we could say that people should expect that there are some dependent packages updates, too, so we could indeed go forward with using v1.11.3, but otherwise, I believe that library development practices say that you should be as broadly supported; in this case highest version with vulnerability fix, lowest version that has that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be updated again I think =D
Upgrade to first next version of
Azure.Idenity
that is not vulnerable in the Azure Key vault secret provider package.