From 39a1661e050584685c0bdd5b95c9bc6de6b4f33e Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Mon, 8 Sep 2025 13:23:04 +0100 Subject: [PATCH] DOC-5709 fixed dodgy note formatting --- .../integrate/redis-data-integration/data-pipelines/deploy.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/integrate/redis-data-integration/data-pipelines/deploy.md b/content/integrate/redis-data-integration/data-pipelines/deploy.md index 0da6ab87a6..3ecbe2b631 100644 --- a/content/integrate/redis-data-integration/data-pipelines/deploy.md +++ b/content/integrate/redis-data-integration/data-pipelines/deploy.md @@ -52,7 +52,9 @@ secrets are only relevant for TLS/mTLS connections. {{< note >}}When creating secrets for TLS or mTLS, ensure that all certificates and keys are in `PEM` format. The only exception to this is that for PostgreSQL, the private key `SOURCE_DB_KEY` secret must be in `DER` format. If you have a key in `PEM` format, you must convert it to `DER` before creating the `SOURCE_DB_KEY` secret using the command: ```bash -openssl pkcs8 -topk8 -inform PEM -outform DER -in /path/to/myclient.pem -out /path/to/myclient.pk8 -nocrypt +openssl pkcs8 -topk8 -inform PEM -outform DER \ + -in /path/to/myclient.pem \ + -out /path/to/myclient.pk8 -nocrypt ``` This command assumes that the private key is not encrypted. See the [`openssl` documentation](https://docs.openssl.org/master/) to learn how to convert an encrypted private key.