Difference between revisions of "Sops --decrypt"
Jump to navigation
Jump to search
Line 33: | Line 33: | ||
== See also == | == See also == | ||
* {{sops}} | * {{sops}} | ||
+ | * {{SoPS}} | ||
[[Category:Secrets]] | [[Category:Secrets]] |
Revision as of 18:08, 9 October 2022
--decrypt, -d sops --decrypt --in-place
sops -d contrib/helm/efi/secrets_prod.yaml (no output) File will be unencrypted and replated.
Errors
sops -d contrib/helm/your-aplication/secrets_prod.yaml > /tmp/decrypted_secrets_prod.yaml Failed to get the data key required to decrypt the SOPS file. Group 0: FAILED projects/your-project/locations/global/keyRings/sops/cryptoKeys/sops-encryption-key: FAILED - | Error decrypting key: googleapi: Error 403: Permission | 'cloudkms.cryptoKeyVersions.useToDecrypt' denied on resource | 'projects/your-project/locations/global/keyRings/sops/cryptoKeys/sops-encryption-key' | (or it may not exist)., forbidden 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. Solution: Cloud KMS CryptoKey Encrypter/Decrypter
Related
See also
Advertising: