mirror of
https://github.com/Mic92/sops-nix.git
synced 2024-12-14 11:57:52 +00:00
Add some helpful tips to the README
A couple notes that tripped me up when initially trying this. I hope they can help make future journeys smoother :) - Getting the syntax of `.sops.yaml` wrong can cause vague errors when it comes to encrypting secrets files. - `path_regex` needs to include all file extensions that you intend to encrypt. `sops` supports YAML, JSON, ENV, INI and binary files, so suggesting that those be picked up by default seems sensible. Personally, I had trouble figuring out why `sops` wouldn't accept my `.env` file - again with a confusing error message.
This commit is contained in:
parent
b2047c8fc9
commit
b1aa4e7107
1 changed files with 9 additions and 4 deletions
13
README.md
13
README.md
|
@ -214,7 +214,7 @@ uid [ unknown] root <root@localhost>
|
|||
The fingerprint here is `9F89C5F69A10281A835014B09C3DC61F752087EF`.
|
||||
</details>
|
||||
|
||||
Your `age` public key or GPG fingerprint can written to your [`.sops.yaml`](https://github.com/mozilla/sops#using-sops-YAML-conf-to-select-kms-pgp-for-new-files) in the root of your configuration directory or repository:
|
||||
Your `age` public key or GPG fingerprint can be written to your [`.sops.yaml`](https://github.com/mozilla/sops#using-sops-YAML-conf-to-select-kms-pgp-for-new-files) in the root of your configuration directory or repository:
|
||||
```yaml
|
||||
# This example uses YAML anchors which allows reuse of multiple keys
|
||||
# without having to repeat yourself.
|
||||
|
@ -224,7 +224,7 @@ keys:
|
|||
- &admin_alice 2504791468b153b8a3963cc97ba53d1919c5dfd4
|
||||
- &admin_bob age12zlz6lvcdk6eqaewfylg35w0syh58sm7gh53q5vvn7hd7c6nngyseftjxl
|
||||
creation_rules:
|
||||
- path_regex: secrets/[^/]+\.yaml$
|
||||
- path_regex: secrets/[^/]+\.(yaml|json|env|ini)$
|
||||
key_groups:
|
||||
- pgp:
|
||||
- *admin_alice
|
||||
|
@ -232,6 +232,11 @@ creation_rules:
|
|||
- *admin_bob
|
||||
```
|
||||
|
||||
**Note:** be sure to not include a `-` before subsequent key types under `key_groups`
|
||||
(i.e. `age` in the above example should not have a `-` in front). If you do, `sops`
|
||||
will produce [a vague error](https://github.com/getsops/sops/issues/857) when
|
||||
encrypting files.
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
|
@ -268,7 +273,7 @@ keys:
|
|||
- &server_azmidi 0fd60c8c3b664aceb1796ce02b318df330331003
|
||||
- &server_nosaxa age1rgffpespcyjn0d8jglk7km9kfrfhdyev6camd3rck6pn8y47ze4sug23v3
|
||||
creation_rules:
|
||||
- path_regex: secrets/[^/]+\.yaml$
|
||||
- path_regex: secrets/[^/]+\.(yaml|json|env|ini)$
|
||||
key_groups:
|
||||
- pgp:
|
||||
- *admin_alice
|
||||
|
@ -276,7 +281,7 @@ creation_rules:
|
|||
age:
|
||||
- *admin_bob
|
||||
- *server_nosaxa
|
||||
- path_regex: secrets/azmidi/[^/]+\.yaml$
|
||||
- path_regex: secrets/azmidi/[^/]+\.(yaml|json|env|ini)$
|
||||
key_groups:
|
||||
- pgp:
|
||||
- *admin_alice
|
||||
|
|
Loading…
Reference in a new issue