clients.ClientBuilder should support tls.Config and clients.SecurityBuilder.

[joshua-rutherford]

As written, the example on the README.md suggests that a ClientBuilder.WithSecurity accepts a tls.Config (i.e., the result of SecurityBuilder.Build()) but that is not the case. It requires a SecuirtyConfig. I think a more appropriate approach would be to support the following signatures:

func (b *ClientBuilder) WithSecuirtyBuilder(builder *SecurityBuilder) *ClientBuilder {...}

func (b *ClientBuilder) WithTLS(config *tls.Config) *ClientBuilder {...}

To do this we'd need to define the precedence order which can be arbitrary but must be documented.

[joshua-rutherford]

@critterjohnson, do you think you can take this on?

[izzy-shirron]

@joshua-rutherford to make the new function WithTLS do I need to add a *tls.configto the ClientConfig struct or the SceurityConfig struct?

[joshua-rutherford]

See the above examples, these methods are being added to the ClientBuilder.