Skip to content

add ability to create a client with own tls connector#606

Closed
seanmonstar wants to merge 1 commit into0.9.xfrom
custom-tls-any
Closed

add ability to create a client with own tls connector#606
seanmonstar wants to merge 1 commit into0.9.xfrom
custom-tls-any

Conversation

@seanmonstar
Copy link
Copy Markdown
Owner

Adapts #562. Instead of the builder method returning a bool, the build call will return an error if it didn't understand the Any value.

@jethrogb
Copy link
Copy Markdown

jethrogb commented Sep 7, 2019

LGTM @Goirad can you review?

@Goirad
Copy link
Copy Markdown

Goirad commented Sep 9, 2019

Also looks good to me

@nicklan
Copy link
Copy Markdown
Contributor

nicklan commented Feb 14, 2020

is this blocked on anything (other than resolving the conflicts)? I'd like to use this feature as soon as its available.

@seanmonstar
Copy link
Copy Markdown
Owner Author

@nicklan I believe I mostly just forgot about this. After a rebase, this could probably merge. I have the slightest inner feeling that it's not the best solution, but don't have a better suggestion, so 🤷‍♂ .

@nicklan
Copy link
Copy Markdown
Contributor

nicklan commented Feb 17, 2020

Okay cool. I agree it's not super elegant, but I think it's better than maintaining your own api to abstract over all possible backends.

@nicklan
Copy link
Copy Markdown
Contributor

nicklan commented Feb 18, 2020

I rebased this and made a new PR at #809. Would be great if it could get merged :)

@seanmonstar
Copy link
Copy Markdown
Owner Author

Merged via #809.

@seanmonstar seanmonstar deleted the custom-tls-any branch February 21, 2020 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants