From 49f8f05c4ba1d184697d0375611c27314b795c52 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?D=C4=81vis?= Date: Wed, 6 May 2026 15:52:18 +0300 Subject: [PATCH 1/3] Clarify encryption and decryption command usage Added notes on output file flag and IDE autoformatting issues. --- docs/encrypting_sensitive_configuration.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/encrypting_sensitive_configuration.md b/docs/encrypting_sensitive_configuration.md index 8e4355d..bee2641 100644 --- a/docs/encrypting_sensitive_configuration.md +++ b/docs/encrypting_sensitive_configuration.md @@ -42,7 +42,7 @@ Or, if you have the encryption key stored as a local environment variable, use t silta secrets encrypt --file /path/to/file --secret-key-env ENV_VAR_NAME ``` -Note that `silta secrets encrypt` encrypts the source file itself unless you specify a different target path via the `--output-file` flag (see full docs [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_encrypt.md)) +Note that `silta secrets encrypt` encrypts the source file itself unless you specify a different target path via the `--output-file` flag (see full docs [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_encrypt.md)). ### 3. Add decryption to CircleCI configuration @@ -117,7 +117,8 @@ or, if you have secret key stored as local environment variable: silta secrets decrypt --file /path/to/encrypted/file --secret-key-env ENV_VAR_NAME ``` -Note that `silta secrets decrypt` decrypts the source file itself unless you specify the`--output-file` flag. See full docs of the decryption command [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_decrypt.md) +Note #1 that `silta secrets decrypt` decrypts the source file itself unless you specify the`--output-file` flag. See full docs of the decryption command [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_decrypt.md). +Note #2: Users of vscode and other IDE users - if enabled, the autoformat functionality may cause for binary or decrypted files to be slightly UTF-8 adjusted which leads to a corrupt sercrets file. Thus it's recommended to use `--output-file` as it will bypass IDE file watch / autoformat functionality. Remember **not to** commit decrypted secret files! From 0844ce8199237e526819a79851fcecaee1b17c2a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?D=C4=81vis?= Date: Wed, 6 May 2026 15:56:11 +0300 Subject: [PATCH 2/3] Formatting fix --- docs/encrypting_sensitive_configuration.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/encrypting_sensitive_configuration.md b/docs/encrypting_sensitive_configuration.md index bee2641..957fd1a 100644 --- a/docs/encrypting_sensitive_configuration.md +++ b/docs/encrypting_sensitive_configuration.md @@ -42,7 +42,7 @@ Or, if you have the encryption key stored as a local environment variable, use t silta secrets encrypt --file /path/to/file --secret-key-env ENV_VAR_NAME ``` -Note that `silta secrets encrypt` encrypts the source file itself unless you specify a different target path via the `--output-file` flag (see full docs [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_encrypt.md)). +crNote that `silta secrets encrypt` encrypts the source file itself unless you specify a different target path via the `--output-file` flag (see full docs [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_encrypt.md)). ### 3. Add decryption to CircleCI configuration @@ -117,8 +117,9 @@ or, if you have secret key stored as local environment variable: silta secrets decrypt --file /path/to/encrypted/file --secret-key-env ENV_VAR_NAME ``` -Note #1 that `silta secrets decrypt` decrypts the source file itself unless you specify the`--output-file` flag. See full docs of the decryption command [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_decrypt.md). -Note #2: Users of vscode and other IDE users - if enabled, the autoformat functionality may cause for binary or decrypted files to be slightly UTF-8 adjusted which leads to a corrupt sercrets file. Thus it's recommended to use `--output-file` as it will bypass IDE file watch / autoformat functionality. +Note that `silta secrets decrypt` decrypts the source file itself unless you specify the`--output-file` flag. See full docs of the decryption command [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_decrypt.md). + +Note for users of vscode and other IDE users - if enabled, the autoformat functionality may cause for binary or decrypted files to be slightly UTF-8 adjusted which leads to a corrupt sercrets file. Thus it's recommended to use `--output-file` as it will bypass IDE file watch / autoformat functionality. Remember **not to** commit decrypted secret files! From a0ba61ff3a5ba0cf8d67eb7737d234e71eff35ab Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?D=C4=81vis?= Date: Wed, 6 May 2026 16:20:45 +0300 Subject: [PATCH 3/3] Typo fix. --- docs/encrypting_sensitive_configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/encrypting_sensitive_configuration.md b/docs/encrypting_sensitive_configuration.md index 957fd1a..f47e998 100644 --- a/docs/encrypting_sensitive_configuration.md +++ b/docs/encrypting_sensitive_configuration.md @@ -42,7 +42,7 @@ Or, if you have the encryption key stored as a local environment variable, use t silta secrets encrypt --file /path/to/file --secret-key-env ENV_VAR_NAME ``` -crNote that `silta secrets encrypt` encrypts the source file itself unless you specify a different target path via the `--output-file` flag (see full docs [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_encrypt.md)). +Note that `silta secrets encrypt` encrypts the source file itself unless you specify a different target path via the `--output-file` flag (see full docs [here](https://github.com/wunderio/silta-cli/blob/master/docs/silta_secrets_encrypt.md)). ### 3. Add decryption to CircleCI configuration