Repository navigation
Investigate if a transport parameter is needed for REST LRO client classes #15032
Closed as not planned
Description
We currently have separate client classes for each combination of [async, sync] x [gRPC, REST] transports. We also maintain separate transport classes for REST.
Given the above case, it's worth figuring out if a transport parameter adds any value in the REST client classes.
Activity
parthea commentedon Jan 12, 2026
Transferring to google-cloud-python as the code for python-api-core will be migrated there in 1-3 weeks.
daniel-sanche commentedon May 27, 2026
This issue is being closed as part of a bulk review (Filter #1). Please reopen if you believe this is still relevant and requires action.