-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Open
Labels
Azure.CoreClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK team
Description
Right now, we can support redirect of AiohttpTransport, TrioTransport (naming*), and RequestsTransport. We need to add a fourth one for HttpxTransport in general.
I had a chat with @mccoyp to discuss how we wanted to resolve this going forward. Effectively, this is what we have right now:
recorded_testpytest fixture- If run from
syncfunction, patchesRequestsTransport.send - If run from
asyncfunction, patchesAiohttpTransport.send
- If run from
@recorded_by_proxydecorator- patches
RequestsTransport.send
- patches
@recorded_by_proxy_asyncdecorator- patches
AiohttpTransport.Send
- patches
The thing is, our implementations across these locations is not shared. We definitely think that we should support individual, customizable patches as stacks, eg:
@recorded_by_proxy
@recorded_by_proxy_httpx
def test_function_that_calls_both_requests_and_httpx_sync()
...Before we do that, we need to refactor to share implementation. That way only the very top level definition of the name of the decorator or feature is passed, and the same common implementation will be used regardless of which one is activated.
mccoyp
Metadata
Metadata
Labels
Azure.CoreClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK team
Type
Projects
Status
π Dev