Skip to content

Upgrade azidentity to v1.5.2#746

Merged
mostynb merged 1 commit intobuchgr:masterfrom
gplessis:azidentity_upgrade
May 11, 2024
Merged

Upgrade azidentity to v1.5.2#746
mostynb merged 1 commit intobuchgr:masterfrom
gplessis:azidentity_upgrade

Conversation

@gplessis
Copy link
Copy Markdown
Contributor

I'm working on setting up bazel-remote in a Kubernetes cluster, as a proxy on top of an Azure Storage Account. To avoid injecting static credentials into the deployment, I would like to configure Entra Workload ID (tl;dr: the resulting pod is mutated and temporary credentials are injected as environment variables).

Unfortunately, the minimum required version of azidentity that supports Workload ID via the default authentication method is v1.3.0.

This PR updates it to it latest version (v1.5.2) from v1.1.0.

Copy link
Copy Markdown
Collaborator

@mostynb mostynb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the submission- this looks good.

IIRC the go azure sdk made a bunch of breaking changes since the azblob feature was added here, but I am unable to easily update it since I don't have an azure account to test against. If you would like to try upgrading that, PRs would be welcome.

@mostynb mostynb merged commit ccc5718 into buchgr:master May 11, 2024
@gplessis
Copy link
Copy Markdown
Contributor Author

Sounds good 👍 When do you think the next release will be cut?

@mostynb
Copy link
Copy Markdown
Collaborator

mostynb commented May 13, 2024

I'm trying to help get #740 landed this week, once that's done it might be a good time for a new release. And if it looks like that PR will take too long, then I can probably make a release at the end of this week.

@gplessis gplessis deleted the azidentity_upgrade branch May 13, 2024 21:47
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.

2 participants