DOCS - Fix secrets typo (#22891)

This commit is contained in:
Pere Miquel Brull 2025-08-11 20:48:45 -07:00 committed by GitHub
parent c5b9e1620f
commit 2525e40db1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 3 additions and 3 deletions

View File

@ -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}`.

View File

@ -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}`.

View File

@ -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}`.