Runtime config is mistakenly reused across clients re-instantiation

[AllanZhengYP]

Describe the bug

This is discovered when investigating #2550, the HTTP/2 request handler is reused across the re-instantiation of TranscribeStreamingClient. The root cause is that the client's runtime config is exported as constant. When user constructs different TranscribeStreamingClient, the same runtime config is reused. As a result, same http client is used across the clients, similar to other configs like credential provider.

Your environment

SDK version number

@aws-sdk/client-transcribe-streaming@3.*.*

Is the issue in the browser/Node.js/ReactNative?

Browser & Node.js & ReactNative

Details of the browser/Node.js/ReactNative version

Paste output of npx envinfo --browsers or node -v or react-native -v

Steps to reproduce

const client1 = new TranscribeStreamingClient({});
const client2 = new TranscribeStreamingClient({});
console.log(client1.config.requestHandler === client2.config.requestHandler);
// prints true

Observed behavior

Different clients use the same request handler.

Expected behavior

They should not use the same handler.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.