feat: Expose a connection string parsing API

Is your feature request related to a problem? Please describe. I want to log the endpoint Uri (but not the key of course), but all I have is a connection string

Describe the solution you’d like var (uri,key) = CosmosClient.ParseConnectionString(connectionString)

Describe alternatives you’ve considered https://stackoverflow.com/a/66746588/11635

Additional context I’ve previously arrived at this (not my original work), and wan’t to do better than that without replicating the logic @NoahStahl found.

[bartelink]

@ealsur I know I can (and thanks for trying to help) - I actually have, for now. I happen even to be able to squirrel it away in a wrapper lib without too much junk leaking into normal apps.

My point, and the reason for this issue, is that the SDK should provide an affordance that lets me naturally emit the Endpoint Uri for diagnostic purposes before I [fail to] ConnectAndInitializeAsync. For the normal lazy-initialized path, a credible solution exists: use CosmosClient.Endpoint - me re-implementing clones of internal behavior of the SDK is not a good solution overall though. I’m raising this issue in the hope e.g. that the V4 SDK provides a better overall answer.

While I’m overstepping the mark, I’m wondering whether overloading of constructors and CreateAndInitializeAsync by a) Connection String b) Endpoint and Key is sustainable and/or will become hard to maintain/add new mechanisms to over time.

[ealsur]

@bartelink you can use System.Data.Common.DbConnectionStringBuilder

DbConnectionStringBuilder builder = new DbConnectionStringBuilder
            {
                ConnectionString = connectionString
            };

            if (builder.TryGetValue("AccountKey", out object key))
            {
                AuthKey = key.ToString();
            }

            if (builder.TryGetValue("AccountEndpoint", out object uri))
            {
                ServiceEndpoint = new Uri(uri.ToString());
            }