Skip to content

Commit 681e16b

Browse files
committed
Mention all stores in various places.
Signed-off-by: Felix Fontein <felix@fontein.de>
1 parent c64b08d commit 681e16b

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1477,7 +1477,7 @@ original file after encrypting or decrypting it.
14771477
Encrypting binary files
14781478
~~~~~~~~~~~~~~~~~~~~~~~
14791479
1480-
SOPS primary use case is encrypting YAML and JSON configuration files, but it
1480+
SOPS primary use case is encrypting YAML, JSON, ENV, and INI configuration files, but it
14811481
also has the ability to manage binary files. When encrypting a binary, SOPS will
14821482
read the data as bytes, encrypt it, store the encrypted base64 under
14831483
``tree['data']`` and write the result as JSON.
@@ -1611,9 +1611,9 @@ git client interfaces, because they call git diff under the hood!
16111611
Encrypting only parts of a file
16121612
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
16131613
1614-
Note: this only works on YAML and JSON files, not on BINARY files.
1614+
Note: this only works on YAML, JSON, ENV, and INI files, not on BINARY files.
16151615
1616-
By default, SOPS encrypts all the values of a YAML or JSON file and leaves the
1616+
By default, SOPS encrypts all the values of a YAML, JSON, ENV, or INI file and leaves the
16171617
keys in cleartext. In some instances, you may want to exclude some values from
16181618
being encrypted. This can be accomplished by adding the suffix **_unencrypted**
16191619
to any key of a file. When set, all values underneath the key that set the
@@ -1824,9 +1824,9 @@ automation, we found this to be a hard problem with a number of prerequisites:
18241824
git repo, jenkins and S3) and only be decrypted on the target
18251825
systems
18261826
1827-
SOPS can be used to encrypt YAML, JSON and BINARY files. In BINARY mode, the
1827+
SOPS can be used to encrypt YAML, JSON, ENV, INI, and BINARY files. In BINARY mode, the
18281828
content of the file is treated as a blob, the same way PGP would encrypt an
1829-
entire file. In YAML and JSON modes, however, the content of the file is
1829+
entire file. In YAML, JSON, ENV, and INI modes, however, the content of the file is
18301830
manipulated as a tree where keys are stored in cleartext, and values are
18311831
encrypted. hiera-eyaml does something similar, and over the years we learned
18321832
to appreciate its benefits, namely:

0 commit comments

Comments
 (0)