@@ -96,7 +96,7 @@ separated, in the **SOPS_PGP_FP** env variable.
9696
9797 Note: you can use both PGP and KMS simultaneously.
9898
99- Then simply call SOPS with a file path as argument. It will handle the
99+ Then simply call `` sops `` with a file path as argument. It will handle the
100100encryption/decryption transparently and open the cleartext file in an editor
101101
102102.. code :: sh
@@ -389,7 +389,7 @@ To easily deploy Vault locally: (DO NOT DO THIS FOR PRODUCTION!!!)
389389Adding and removing keys
390390~~~~~~~~~~~~~~~~~~~~~~~~
391391
392- When creating new files, SOPS uses the PGP, KMS and GCP KMS defined in the
392+ When creating new files, ` ` sops ` ` uses the PGP, KMS and GCP KMS defined in the
393393command line arguments ` ` --kms` ` , ` ` --pgp` ` , ` ` --gcp-kms` ` or ` ` --azure-kv` ` , or from
394394the environment variables ` ` SOPS_KMS_ARN` ` , ` ` SOPS_PGP_FP` ` , ` ` SOPS_GCP_KMS_IDS` ` ,
395395` ` SOPS_AZURE_KEYVAULT_URLS` ` . That information is stored in the file under the
@@ -601,8 +601,8 @@ roles that can only access a given context. An example policy is shown below:
601601Key Rotation
602602~~~~~~~~~~~~
603603
604- It is recommended to renew the data key on a regular basis. SOPS supports key
605- rotation via the ` ` -r` ` flag. Invoking it on an existing file causes SOPS to
604+ It is recommended to renew the data key on a regular basis. ` ` sops ` ` supports key
605+ rotation via the ` ` -r` ` flag. Invoking it on an existing file causes ` ` sops ` ` to
606606reencrypt the file with a new data key, which is then encrypted with the various
607607KMS and PGP master keys defined in the file.
608608
@@ -1146,7 +1146,7 @@ extension after encrypting a file. For example:
11461146 $ sops -d myfile.json
11471147
11481148If you want to change the extension of the file once encrypted, you need to provide
1149- SOPS with the ` ` --input-type` ` flag upon decryption. For example:
1149+ ` ` sops ` ` with the ` ` --input-type` ` flag upon decryption. For example:
11501150
11511151.. code:: sh
11521152
@@ -1267,7 +1267,7 @@ Encrypting an existing file
12671267~~~~~~~~~~~~~~~~~~~~~~~~~~~
12681268
12691269Similar to the previous command, we tell SOPS to use one KMS and one PGP key.
1270- The path points to an existing cleartext file, so we give SOPS flag ``-e`` to
1270+ The path points to an existing cleartext file, so we give ``sops`` the flag ``-e`` to
12711271encrypt the file, and redirect the output to a destination file.
12721272
12731273.. code:: sh
@@ -1285,7 +1285,7 @@ Decrypt the file with ``-d``.
12851285Encrypt or decrypt a file in place
12861286~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
12871287
1288- Rather than redirecting the output of ``-e`` or ``-d``, SOPS can replace the
1288+ Rather than redirecting the output of ``-e`` or ``-d``, ``sops`` can replace the
12891289original file after encrypting or decrypting it.
12901290
12911291.. code:: sh
0 commit comments