"couchbases://" Does not automatically enable TLS in SDK 3.4

/ -

I don't think this is an introduced bug/regression as there is a unit test that explicitly tests that if the ConfigProfile.EnableTls is false and "couchbases" schema is used the effective TLS setting is disabled. I see this test going back all versions, so the behavior has always been that the EnableTls flag must be true or null no matter if the passed in schema from the connection string was "couchbases":

• https://github.com/couchbase/couchbase-net-client/blob/3.4.0/tests/Couchbase.UnitTests/ClusterOptionsTests.cs#L110

• https://github.com/couchbase/couchbase-net-client/blob/3.3.0/tests/Couchbase.UnitTests/ClusterOptionsTests.cs#L64

• https://github.com/couchbase/couchbase-net-client/blob/3.2.0/tests/Couchbase.UnitTests/ClusterOptionsTests.cs#L58

• https://github.com/couchbase/couchbase-net-client/blob/3.1.0/tests/Couchbase.UnitTests/ClusterOptionsTests.cs#L36

• https://github.com/couchbase/couchbase-net-client/blob/3.0.0/tests/Couchbase.UnitTests/ClusterOptionsTests.cs#L36

I think we can simply call it a bug and it should be easily fixable by EOW for 3.4.1.

Jeff

What is the ETA for this fix?