How to Setup SOPS on windows? Please share me doc if any.
Using it on Linux based os, want to try it on windows (local), didn't succeed so far. Please share doc for the same.
Do you have a more specific question? The answer is "the same way you would on Linux", as far as I can tell. Download the binary and run it.
There is should be some note in the documentation, that it is a single binary for Windows, not the installer.
It should be placed somewhere on the disk and added to the PATH variable.
I cannot find any documentation for windows, only for linux. Can this thing be installed on win 10?
@diegocejasprieto You can configure SOPS tool on Windows manually:
- Download latest sops-v3.9.1.exe
- Copy the tool to the C:\Program Files (x86)\Sops\v3.9.1 folder and rename to sops.exe
- Open "Environment Variables" window and add C:\Program Files (x86)\Sops\v3.9.1 to the PATH variable
- Open CMD and try:
sops -v
You can also install it through Chocolatey package manager https://community.chocolatey.org/packages/sops
I have successfully installed sops with Chocolatey on Windows 11. But sops is failing. I'm specifying my AWS profile with --aws-profile (credentials are stored in my users home C:\Users\username\.aws\credentials) and the sops config file .sops.yaml (having the kms key) is in the projects root.
Error message received:
Group 0: FAILED
arn:aws:kms:
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.
Am I missing any configuration step?
I found this article that can help you https://blog.gitguardian.com/a-comprehensive-guide-to-sops/
Well this is a nice article about sops indeed but it doesn't help to fix the issue I face when executing sops on Windows 11.
I finally got it to work! It does only work if the profile is stored as an environmental variable. To execute sops in Powershell and set the environmental variable for this command only you can execute it with a subshell: powershell -Command { $env:AWS_PROFILE="profilename"; sops secret-file.yaml }