getsops/sops
1
0
Fork 0
mirror of https://github.com/getsops/sops.git synced 2026-02-05 12:45:21 +01:00
Code Issues Activity

Wrapped lines, moved note below the code sample

Browse Source
This commit is contained in:
Adrian Utrilla
2016-10-26 17:12:12 +02:00
committed by GitHub
parent 12a1217286
commit 0671d1faf8
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
README.rst
View File

@@ -94,9 +94,7 @@ separated, in the **SOPS_PGP_FP** env variable.
Note: you can use both PGP and KMS simultaneously.
Then simply call `sops` with a file path as argument. It will handle the
encryption/decryption transparently and open the cleartext file in an editor.
Editing will happen in whatever $EDITOR is set to, or, if it's not set, in vim.
Keep in mind that sops will wait for the editor to exit, and then try to reencrypt the file. Some GUI editors (atom, sublime) spawn a child process and then exit immediately. They usually have an option to wait for the main editor window to be closed before exiting. See [#127](https://github.com/mozilla/sops/issues/127) for more information.
encryption/decryption transparently and open the cleartext file in an editor
.. code:: bash
@@ -105,6 +103,14 @@ Keep in mind that sops will wait for the editor to exit, and then try to reencry
please wait while an encryption key is being generated and stored in a secure fashion
file written to mynewtestfile.yaml
.
Editing will happen in whatever $EDITOR is set to, or, if it's not set, in vim.
Keep in mind that sops will wait for the editor to exit, and then try to reencrypt
the file. Some GUI editors (atom, sublime) spawn a child process and then exit
immediately. They usually have an option to wait for the main editor window to be
closed before exiting. See [#127](https://github.com/mozilla/sops/issues/127) for
more information.
The resulting encrypted file looks like this:
.. code:: yaml