You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"title": "The default Qdrant database collection configuration\nThis is an optional field"
874
+
"description": "The default Qdrant database collection configuration.\nThis setting is for both managed and hybrid cloud clusters, see sub-messages for more details.\nThis is an optional field."
"title": "The default Qdrant database storage configuration\nThis is an optional field"
878
+
"description": "The default Qdrant database storage configuration.\nThis setting is for both managed and hybrid cloud clusters.\nThis is an optional field."
"title": "The Qdrant database service configuration\nThis is an optional field"
882
+
"title": "The Qdrant database service configuration\nThis setting is for both managed and hybrid cloud clusters, see sub-messages for more details.\nThis is an optional field"
"title": "The log level for the database\nThis is an optional field, default is Info.\nQdrant is written in Rust and is using: https://docs.rs/log/latest/log/enum.LevelFilter.html"
886
+
"description": "The log level for the database.\nQdrant is written in Rust and is using: https://docs.rs/log/latest/log/enum.LevelFilter.html\nThis setting is for hybrid cloud clusters only, it is ignored for managed cloud clusters.\nThis is an optional field, default is Info."
"title": "The Qdrant database TLS configuration\nThis is an optional field, if not set an unsecure connection is provided"
890
+
"description": "The Qdrant database TLS configuration.\nThis setting is for hybrid cloud clusters only, it is ignored for managed cloud clusters.\nThis is an optional field, if not set an unsecure connection is provided."
"title": "The Qdrant database inference configuration\nThis is an optional field, if unset, the database is not configured for cloud inferencing"
894
+
"title": "The Qdrant database inference configuration.\nThis setting is for managed cloud clusters only, it is ignored for hybrid cloud clusters.\nThis is an optional field, if unset, the database is not configured for cloud inferencing"
895
895
}
896
896
},
897
-
"description": "Configuration to setup a Qdrant database in a hybrid cloud.\nAll settings apply to hybrid cloud only."
897
+
"description": "Configuration to setup a Qdrant database.\nThe settings apply to managed and/or hybrid cloud, see documentation on each message for more details."
898
898
},
899
899
"v1DatabaseConfigurationCollection": {
900
900
"type": "object",
@@ -956,19 +956,19 @@
956
956
"properties": {
957
957
"apiKey": {
958
958
"$ref": "#/definitions/v1SecretKeyRef",
959
-
"title": "Set an api-key.\nIf set, all requests must include a header with the api-key.\nexample header: `api-key: \u003cAPI-KEY\u003e`"
959
+
"title": "Set an api-key.\nThis setting is for hybrid cloud clusters only, for managed cloud please use qdrant.cloud.cluster.auth.[v1|v2].DatabaseApiKeyService to configure keys.\nIf set, all requests must include a header with the api-key.\nexample header: `api-key: \u003cAPI-KEY\u003e`"
960
960
},
961
961
"readOnlyApiKey": {
962
962
"$ref": "#/definitions/v1SecretKeyRef",
963
-
"title": "Set an api-key for read-only operations.\nIf set, all requests must include a header with the api-key.\nexample header: `api-key: \u003cAPI-KEY\u003e`"
963
+
"title": "Set an api-key for read-only operations.\nThis setting is for hybrid cloud clusters only, for managed cloud please use qdrant.cloud.cluster.auth.[v1|v2].DatabaseApiKeyService to configure keys.\nIf set, all requests must include a header with the api-key.\nexample header: `api-key: \u003cAPI-KEY\u003e`"
964
964
},
965
965
"jwtRbac": {
966
966
"type": "boolean",
967
-
"description": "Enable JWT Role Based Access Control (RBAC).\nIf enabled, you can generate JWT tokens with fine-grained rules for access control.\nUse generated token instead of API key."
967
+
"description": "Enable JWT Role Based Access Control (RBAC).\nThis setting is for both managed and hybrid cloud clusters.\nIf enabled, you can generate JWT tokens with fine-grained rules for access control.\nUse generated token instead of API key."
968
968
},
969
969
"enableTls": {
970
970
"type": "boolean",
971
-
"title": "Enable HTTPS for the REST and gRPC API"
971
+
"description": "Enable HTTPS for the REST and gRPC API\nThis setting is for hybrid cloud clusters only, for managed cloud clusters the platform controls it (and clients need to use a secure connection)."
972
972
}
973
973
},
974
974
"title": "The Qdrant database service configuration"
* This setting is for hybrid cloud clusters only, for managed cloud please use qdrant.cloud.cluster.auth.[v1|v2].DatabaseApiKeyService to configure keys.
851
858
* If set, all requests must include a header with the api-key.
852
859
* example header: `api-key: <API-KEY>`
853
860
*
@@ -857,6 +864,7 @@ export declare type DatabaseConfigurationService = Message<"qdrant.cloud.cluster
857
864
858
865
/**
859
866
* Set an api-key for read-only operations.
867
+
* This setting is for hybrid cloud clusters only, for managed cloud please use qdrant.cloud.cluster.auth.[v1|v2].DatabaseApiKeyService to configure keys.
860
868
* If set, all requests must include a header with the api-key.
861
869
* example header: `api-key: <API-KEY>`
862
870
*
@@ -866,6 +874,7 @@ export declare type DatabaseConfigurationService = Message<"qdrant.cloud.cluster
866
874
867
875
/**
868
876
* Enable JWT Role Based Access Control (RBAC).
877
+
* This setting is for both managed and hybrid cloud clusters.
869
878
* If enabled, you can generate JWT tokens with fine-grained rules for access control.
870
879
* Use generated token instead of API key.
871
880
*
@@ -875,6 +884,7 @@ export declare type DatabaseConfigurationService = Message<"qdrant.cloud.cluster
875
884
876
885
/**
877
886
* Enable HTTPS for the REST and gRPC API
887
+
* This setting is for hybrid cloud clusters only, for managed cloud clusters the platform controls it (and clients need to use a secure connection).
0 commit comments