sending method as msi but it is using az cli
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Discussed in https://github.com/getsops/sops/discussions/1231
Originally posted by sumanth342 June 29, 2023
sending method as msi but it is using az cli
Group 0: FAILED
│ https://myvault.vault.azure.net/keys/sops-key/: FAILED
│ - | Invoking Azure CLI failed with the following error: exec:
│ | "az": executable file not found in $PATH
│
│ Recovery failed because no master key was able to decrypt the file. In
│ order for SOPS to recover the file, at least one key has to be successful,
│ but none were.
│
│ with data.sops_file.demo-secret,
│ on main.tf line 20, in data "sops_file" "demo-secret":
│ 20: data "sops_file" "demo-secret" {
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 reproducing the Azure key decryption failure with the MSI method and no az executable available, then trace the Azure key retrieval path. Done means SOPS uses MSI authentication rather than invoking Azure CLI and successfully decrypts the file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100