Skip to content

Commit 105cc88

Browse files
committed
Use better note markup.
For some reason https://www.docsy.dev/docs/content/adding-content/#alerts does not work. Signed-off-by: Felix Fontein <felix@fontein.de>
1 parent 656f5a3 commit 105cc88

1 file changed

Lines changed: 20 additions & 10 deletions

File tree

content/en/docs/_index.md

Lines changed: 20 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,9 @@ comma separated, in the **SOPS_PGP_FP** env variable.
100100
export SOPS_PGP_FP="85D77543B3D624B63CEA9E6DBC17301B491B3F21,E60892BB9BD89A69F759A1A0A3D652173B763E8F"
101101
```
102102

103-
Note: you can use both PGP and KMS simultaneously.
103+
> 📝 **Note**
104+
>
105+
> You can use both PGP and KMS simultaneously.
104106
105107
Then simply call `sops edit` with a file path as argument. It will
106108
handle the encryption/decryption transparently and open the cleartext
@@ -787,8 +789,10 @@ stored under a specific directory, like a `git` repository, you can
787789
create a `.sops.yaml` configuration file at the root directory to define
788790
which keys are used for which filename.
789791
790-
Note: The file needs to be named `.sops.yaml`. Other names (i.e. `.sops.yml`) won't be automatically
791-
discovered by sops. You'll need to pass the `--config .sops.yml` option for it to be picked up.
792+
> 📝 **Note**
793+
>
794+
> The file needs to be named `.sops.yaml`. Other names (i.e. `.sops.yml`) won't be automatically
795+
> discovered by sops. You'll need to pass the `--config .sops.yml` option for it to be picked up.
792796
793797
Let\'s take an example:
794798
@@ -1378,8 +1382,10 @@ stores:
13781382
indent: 2
13791383
```
13801384
1381-
Note: The YAML emitter used by sops only supports values between 2 and 9. If
1382-
you specify 1, or 10 and larger, the indent will be 2.
1385+
> 📝 **Note**
1386+
>
1387+
> The YAML emitter used by sops only supports values between 2 and 9. If
1388+
> you specify 1, or 10 and larger, the indent will be 2.
13831389
13841390
### YAML anchors
13851391
@@ -1664,7 +1670,9 @@ the hood!
16641670
16651671
### Encrypting only parts of a file
16661672
1667-
Note: this only works on YAML, JSON, ENV, and INI files, not on BINARY files.
1673+
> 📝 **Note**
1674+
>
1675+
> This only works on YAML, JSON, ENV, and INI files, not on BINARY files.
16681676
16691677
By default, SOPS encrypts all the values of a YAML, JSON, ENV, or INI file and
16701678
leaves the keys in cleartext. In some instances, you may want to exclude
@@ -1724,10 +1732,12 @@ that matches the supplied regular expression.
17241732
17251733
You can also specify these options in the `.sops.yaml` config file.
17261734
1727-
Note: these six options `--unencrypted-suffix`, `--encrypted-suffix`,
1728-
`--encrypted-regex`, `--unencrypted-regex`, `--encrypted-comment-regex`,
1729-
and `--unencrypted-comment-regex` are mutually exclusive and
1730-
cannot all be used in the same file.
1735+
> 📝 **Note**
1736+
>
1737+
> These six options `--unencrypted-suffix`, `--encrypted-suffix`,
1738+
> `--encrypted-regex`, `--unencrypted-regex`, `--encrypted-comment-regex`,
1739+
> and `--unencrypted-comment-regex` are mutually exclusive and
1740+
> cannot all be used in the same file.
17311741
17321742
## Config file format
17331743

0 commit comments

Comments
 (0)