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

Update Azure SDK versions #33

Merged
merged 1 commit into from
Aug 14, 2023
Merged

Conversation

patst
Copy link
Contributor

@patst patst commented Jun 12, 2023

This update updates the azure SDKs:

  • upgrade azidentity to v1.3.0
  • update azcore to v1.6.1

Especially the azidentity part is interesting, because after merging this WorkloadIdentityCredential is available and be used.

This is interesting for authorization inside Azure Kubernetes Service using Workload Identity. See the discussion at grafana/grafana#53645 for details

wdyt?

* upgrade azidentity to v1.3.0
* update azcore to v1.6.1
@CLAassistant
Copy link

CLAassistant commented Jun 12, 2023

CLA assistant check
All committers have signed the CLA.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@patst patst changed the title feat: update Azure SDKs Update Azure SDK versions Jun 12, 2023
@aangelisc
Copy link
Contributor

Thank you for the contribution @patst. I don't think this completely solves the issue mentioned in grafana/grafana#53645 but it will allow us to make use of the DefaultAzureCredential which then solves the problem.

@aangelisc aangelisc merged commit fbabed1 into grafana:main Aug 14, 2023
1 check passed
@patst patst deleted the feat/update-azure-sdk branch August 14, 2023 14:01
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

Successfully merging this pull request may close these issues.

None yet

3 participants