From 2525e40db1a95d562d81bb2282156a5c57ae44cf Mon Sep 17 00:00:00 2001 From: Pere Miquel Brull Date: Mon, 11 Aug 2025 20:48:45 -0700 Subject: [PATCH] DOCS - Fix secrets typo (#22891) --- .../content/v1.7.x/deployment/secrets-manager/index.md | 2 +- .../content/v1.8.x/deployment/secrets-manager/index.md | 2 +- .../content/v1.9.x-SNAPSHOT/deployment/secrets-manager/index.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/openmetadata-docs/content/v1.7.x/deployment/secrets-manager/index.md b/openmetadata-docs/content/v1.7.x/deployment/secrets-manager/index.md index 219c768d5b8..73432e7a82a 100644 --- a/openmetadata-docs/content/v1.7.x/deployment/secrets-manager/index.md +++ b/openmetadata-docs/content/v1.7.x/deployment/secrets-manager/index.md @@ -65,7 +65,7 @@ pipeline. For example, suppose we create a MySQL service with the name `mysql-test`. In that case, the connection password will be stored in the secrets manager using the secret id `/openmetadata/database/mysql-test/password`. When we retrieve the connection parameters from the service, the password field will have the value -`secrets:/openmetadata/database/mysql-test/password`. +`secret:/openmetadata/database/mysql-test/password`. We can also use secrets already stored in our secrets vault using the same convention `secret:{secret_id}`. diff --git a/openmetadata-docs/content/v1.8.x/deployment/secrets-manager/index.md b/openmetadata-docs/content/v1.8.x/deployment/secrets-manager/index.md index 2a14e7b90d2..979028d968b 100644 --- a/openmetadata-docs/content/v1.8.x/deployment/secrets-manager/index.md +++ b/openmetadata-docs/content/v1.8.x/deployment/secrets-manager/index.md @@ -65,7 +65,7 @@ pipeline. For example, suppose we create a MySQL service with the name `mysql-test`. In that case, the connection password will be stored in the secrets manager using the secret id `/openmetadata/database/mysql-test/password`. When we retrieve the connection parameters from the service, the password field will have the value -`secrets:/openmetadata/database/mysql-test/password`. +`secret:/openmetadata/database/mysql-test/password`. We can also use secrets already stored in our secrets vault using the same convention `secret:{secret_id}`. diff --git a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/secrets-manager/index.md b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/secrets-manager/index.md index fc4a5631283..a8731de905f 100644 --- a/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/secrets-manager/index.md +++ b/openmetadata-docs/content/v1.9.x-SNAPSHOT/deployment/secrets-manager/index.md @@ -65,7 +65,7 @@ pipeline. For example, suppose we create a MySQL service with the name `mysql-test`. In that case, the connection password will be stored in the secrets manager using the secret id `/openmetadata/database/mysql-test/password`. When we retrieve the connection parameters from the service, the password field will have the value -`secrets:/openmetadata/database/mysql-test/password`. +`secret:/openmetadata/database/mysql-test/password`. We can also use secrets already stored in our secrets vault using the same convention `secret:{secret_id}`.