From a54afb1a1bbc9706c4bcade49db50dc0c7873da3 Mon Sep 17 00:00:00 2001 From: Ivan De Marino Date: Thu, 28 Jul 2022 18:37:23 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com> --- website/docs/plugin/sdkv2/logging/http-transport.mdx | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/website/docs/plugin/sdkv2/logging/http-transport.mdx b/website/docs/plugin/sdkv2/logging/http-transport.mdx index d5ab726198..f5f47bb9ee 100644 --- a/website/docs/plugin/sdkv2/logging/http-transport.mdx +++ b/website/docs/plugin/sdkv2/logging/http-transport.mdx @@ -27,7 +27,7 @@ To set up HTTP transport, you must create the HTTP Client to use the new transpo ### Creating the HTTP Client -Once the correct _Transport _has been created, it should be used when setting up the `http.Client` that the provider is going to use. For example, a good place to set up the client could be the `schema.Provider` `ConfigureContextFunc`: +After you create the transport , you must use it to set up the `http.Client` for the provider. The following example sets up the client in `schema.Provider` `ConfigureContextFunc`. The client is identical to the default Golang `http.Client`, except it uses the new logging transport. ```go func New() (*schema.Provider, error) { @@ -47,9 +47,6 @@ func New() (*schema.Provider, error) { } } } -``` - -This will set up a client that is identical to the default Golang `http.Client`, except it uses the new logging transport. ## Adding Context to HTTP Requests