Azure KeyVault Go libraries EOL
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
The current Go libraries used for Azure KeyVault access will be out of support by March 31, 2023 https://github.com/Azure/go-autorest Can SOPS please update to use the new libraries for continued use? https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/azidentity
The new version of the identity library also supports ClientAssertionCredential which is need to support authentication with the new workload identity that Azure is rolling out, sample of how it is used can here found here https://github.com/Azure/azure-workload-identity/blob/main/examples/msal-go/main.go#L46
Upgrading the Azure Go authentication libraries before they are out of support and adding a new up and coming authentication method would be greatly appreciated
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating SOPS's current use of github.com/Azure/go-autorest, then compare it with the Azure SDK for Go azidentity library and the ClientAssertionCredential example linked in the issue. Done means Azure Key Vault authentication uses supported libraries and supports the requested workload identity authentication method, with relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100