You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using sops with Terraform and have the same issue as in #818
│ Error: Failed to get the data key required to decrypt the SOPS file.
│
│ Group 0: FAILED
│ https://xxxxxxxx.vault.azure.net/keys/sops-key/xxxxxxxxxxxx: FAILED
│ - | Invoking Azure CLI failed with the following error: 'az' is
│ | not recognized as an internal or external command,
│ | operable program or batch file.
│
│
│ 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.
Calling az works fine and
hich az
/c/Program Files/Microsoft SDKs/Azure/CLI2/wbin/az
The difference to [#818] is, that az is installed with msi not SOPS
The text was updated successfully, but these errors were encountered:
Still an issue when using sops via git bash installed using winget:
$ sops.exe prod.secrets.json
[AZKV] time="2025-02-05T15:01:38+01:00" level=error msg="Failed to create Azure authorizer" error="Invoking Azure CLI failed with the following error: 'az' is not recognized as an internal or external command,\r\noperable program or batch file.\r\n"
Failed to get the data key required to decrypt the SOPS file.
...
$ az
/\
/ \ _____ _ _ ___ _
/ /\ \ |_ / | | | \'__/ _\
/ ____ \ / /| |_| | | | __/
/_/ \_\/___|\__,_|_| \___|
Welcome to the cool new Azure CLI!
I am using sops with Terraform and have the same issue as in #818
Calling
az
works fine andThe difference to [#818] is, that az is installed with msi not SOPS
The text was updated successfully, but these errors were encountered: