Use Azure Key Vault login error
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Hi Team!
I updated my sops version to 3.8.1 from 3.7.3 and I got a problem with Azure Key Vault Service.
With 3.7.3 version I only need to do an "az login" previously to use sops.
With the new version I need to do "az login" and export the environment variables AZURE_CLIENT_ID, AZURE_TENANT_ID and AZURE_CLIENT_SECRET.
If I don't export the environment variables I have the following output:
I was checking the Changelog of the latest versions and I didn't see any change in this kind of work.
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 comparing Azure Key Vault authentication between sops 3.7.3 and 3.8.1, using the reported az login setup without AZURE_CLIENT_ID, AZURE_TENANT_ID, or AZURE_CLIENT_SECRET. Review the relevant changelog entries and reproduce the error shown in the issue. Done when the expected login behavior is restored or the changed requirement is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- authentication, cli, cloud, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100