[Perf Framework] Allow "https" without setting insecure option while using test-proxy

[HarshaNalluru]

Background

#17898 adds the "insecure" option to create an httpsAgent with rejectUnauthorized : false option. Since it is only for testing, we were fine with that.

Passing .pfx with the passphrase is throwing an error as shown below.

This affects both the perf framework and the recorder.

To Repro

• Tweak the httpsAgent in

  azure-sdk-for-js/sdk/test-utils/perfstress/src/utils.ts

  Line 28 in 89a29f2

  export const getCachedHttpsAgent = (insecure: boolean) => {

  
  (uncomment the .pfx related part in the options)
• Go to sdk/storage/perf-tests/storage-blob
• rush update && rush build -t .
• Put .env with STORAGE_CONNECTION_STRING in the same folder
• In a separate terminal, docker run -p 5000:5000 -p 5001:5001 azsdkengsys.azurecr.io/engsys/ubuntu_testproxy_server:latest
• Run the test
  • without proxy-tool
    npm run perf-test:node -- StorageBlobDownloadTest --warmup 2 --duration 7 --iterations 2 --parallel 2
  • with proxy-tool but HTTP
    npm run perf-test:node -- StorageBlobDownloadTest --warmup 2 --duration 7 --iterations 2 --parallel 2 --test-proxy http://localhost:5000
  • with proxy-tool but https
    npm run perf-test:node -- StorageBlobDownloadTest --warmup 2 --duration 7 --iterations 2 --parallel 2 --test-proxy https://localhost:5001

@mikeharder @scbedd @chradek

[github-actions]

Hi @HarshaNalluru, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.