Acceptance Criteria:
The idea is to create two independent environment variables for the below purposes:
-
To route the data plane operations through Thin Client, there would be a new endpoint needed called thinClientEndpoint. However, the source of this new endpoint is still unknown at the moment, and for the purpose of this design, we will assume that this endpoint will be set using an environment variable named as AZURE_COSMOS_THIN_CLIENT_ENDPOINT. When the thin client mode is selected and this endpoint is not provided/ set, the SDK should throw an error suggesting setting the variable.
-
For the first iteration, the thin client mode can be set using an environment variable AZURE_COSMOS_THIN_CLIENT_ENABLED. When set to True, the thin client mode will be activated, and the data plane requests will be routed through the Thin Client.
Acceptance Criteria:
The idea is to create two independent environment variables for the below purposes:
To route the data plane operations through Thin Client, there would be a new endpoint needed called
thinClientEndpoint. However, the source of this new endpoint is still unknown at the moment, and for the purpose of this design, we will assume that this endpoint will be set using an environment variable named asAZURE_COSMOS_THIN_CLIENT_ENDPOINT. When the thin client mode is selected and this endpoint is not provided/ set, the SDK should throw an error suggesting setting the variable.For the first iteration, the thin client mode can be set using an environment variable
AZURE_COSMOS_THIN_CLIENT_ENABLED. When set to True, the thin client mode will be activated, and the data plane requests will be routed through the Thin Client.