From e3ce9ad7dd2f0e6fd33916a9047f53d2292f647d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luis=20Coss=C3=ADo?= Date: Thu, 7 Dec 2023 10:16:58 -0300 Subject: [PATCH] add read-only-api-key configuration example --- .../content/documentation/guides/configuration.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/qdrant-landing/content/documentation/guides/configuration.md b/qdrant-landing/content/documentation/guides/configuration.md index 92bd9ae55..b47cd985c 100644 --- a/qdrant-landing/content/documentation/guides/configuration.md +++ b/qdrant-landing/content/documentation/guides/configuration.md @@ -253,7 +253,7 @@ service: # Set an api-key. # If set, all requests must include a header with the api-key. - # example header: `api-key: ` + # Example header: `api-key: ` # # If you enable this you should also enable TLS. # (Either above or via an external service like nginx.) @@ -261,6 +261,17 @@ service: # # Uncomment to enable. # api_key: your_secret_api_key_here + + # Set an api-key for read-only operations. + # If set, all read requests must include a header with the api-key. + # Example header: `api-key: ` + # + # If you enable this you should also enable TLS. + # (Either above or via an external service like nginx.) + # Sending an api-key over an unencrypted channel is insecure. + # + # Uncomment to enable. + # read_only_api_key: your_secret_read_only_api_key_here cluster: # Use `enabled: true` to run Qdrant in distributed deployment mode