@@ -1130,15 +1130,15 @@ Below is an example of publishing to Vault (using token auth with a local dev in
11301130Important information on types
11311131------------------------------
11321132
1133- YAML and JSON type extensions
1134- ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1133+ YAML, JSON, ENV and INI type extensions
1134+ ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11351135
11361136SOPS uses the file extension to decide which encryption method to use on the file
11371137content. ` ` YAML` ` , ` ` JSON` ` , ` ` ENV` ` , and ` ` INI` ` files are treated as trees of data, and key/values are
11381138extracted from the files to only encrypt the leaf values. The tree structure is also
11391139used to check the integrity of the file.
11401140
1141- Therefore, if a file is encrypted using a specific format, it need to be decrypted
1141+ Therefore, if a file is encrypted using a specific format, it needs to be decrypted
11421142in the same format. The easiest way to achieve this is to conserve the original file
11431143extension after encrypting a file. For example:
11441144
@@ -1165,23 +1165,27 @@ When operating on stdin, use the ``--input-type`` and ``--output-type`` flags as
11651165JSON indentation
11661166~ ~~~~~~~~~~~~~~~
11671167
1168- ` ` sops` ` indent ` ` SOPS` ` files by default using one ` ` tab` ` . However, you can change
1169- this default behaviour to use spaces by either using the additional ` ` --indent=2` ` cli option or
1170- by configuring ` ` .sops.yaml` ` with the code below. (value ` ` 0` ` is no indentation)
1168+ SOPS indents ` ` JSON` ` files by default using one ` ` tab` ` . However, you can change
1169+ this default behaviour to use ` ` spaces` ` by either using the additional ` ` --indent=2` ` CLI option or
1170+ by configuring ` ` .sops.yaml` ` with the code below.
1171+
1172+ The special value ` ` 0` ` disables indentation, and ` ` -1` ` uses a single tab.
11711173
11721174.. code:: yaml
1175+
11731176 stores:
11741177 json:
11751178 indent: 2
11761179
11771180YAML indentation
11781181~ ~~~~~~~~~~~~~~~
11791182
1180- ` ` sops ` ` indent ` ` YAML` ` files by default using 4 spaces. However, you can change
1181- this default behaviour by either using the additional ` ` --indent=2` ` cli option or
1182- by configuring ` ` .sops.yaml` ` with :
1183+ SOPS indents ` ` YAML` ` files by default using 4 spaces. However, you can change
1184+ this default behaviour by either using the additional ` ` --indent=2` ` CLI option or
1185+ by configuring ` ` .sops.yaml` ` with:
11831186
11841187.. code:: yaml
1188+
11851189 stores:
11861190 yaml:
11871191 indent: 2
0 commit comments