extendedRequestId and cfId are not populated in metadata

[trivikr]

Describe the bug
extendedRequestId and cfId are not populated in metadata

• requestId is populated from x-amzn-requestid header which is accessible in httpHeaders

  aws-sdk-js-v3/clients/client-s3/protocols/Aws_restXml.ts

  Lines 12829 to 12833 in a377957

  	const deserializeMetadata = (output: __HttpResponse): __ResponseMetadata => ({
  	httpStatusCode: output.statusCode,
  	httpHeaders: output.headers,
  	requestId: output.headers["x-amzn-requestid"],
  	});

• extendedRequestId used to be populated from x-amz-id-2 header in 0.1.0-preview clients

  aws-sdk-js-v3/packages/response-metadata-extractor/src/index.ts

  Line 21 in 47f1c36

  extendedRequestId: httpHeaders[EXTENDED_REQUEST_ID_HEADER],

• cfId used to be populated from "x-amz-cf-id" header in 0.1.0-preview clients

  aws-sdk-js-v3/packages/response-metadata-extractor/src/index.ts

  Line 22 in 47f1c36

  cfId: httpHeaders[CF_ID_HEADER]

From past experience, quickly getting extendedRequestId and cfId helps with debugging.

SDK version number

    "@aws-sdk/client-s3-control": "1.0.0-gamma.8",
    "@aws-sdk/client-sts": "1.0.0-gamma.8",

To Reproduce (observed behavior)

Code

const { STS } = require("@aws-sdk/client-sts");
const { S3Control } = require("@aws-sdk/client-s3-control");

(async () => {
  const stsClient = new STS({});
  const s3ControlClient = new S3Control({});

  const { Account } = await stsClient.getCallerIdentity({});
  console.log(await s3ControlClient.listAccessPoints({ AccountId: Account }));
})();

Output

{
  '$metadata': {
    httpStatusCode: 200,
    httpHeaders: {
      'x-amz-id-2': 'r7rFiQubPFSqaW+cXofM2hmAYGqtbg5Jj3ctEWwt1cKzx5eFFW5lwrTa6Qn1rdYEZxrlcEQiD5E=',
      'x-amz-request-id': '2516C4C3BADE55E6',
      date: 'Mon, 14 Sep 2020 16:32:45 GMT',
      'content-length': '72',
      server: 'AmazonS3'
    },
    requestId: undefined,
    attempts: 1,
    totalRetryDelay: 0
  },
  __type: 'ListAccessPointsResult',
  AccessPointList: [],
  NextToken: undefined
}

Expected behavior
The value extendedRequestId should be populated in metadata.

[trivikr]

This bug may be fixed by adding new middleware altogether which populates and logs metadata #1491 (comment)

[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.