Send X-Scal-Request-Uids (not x-scal-request-id) on the management config poll#6218
Send X-Scal-Request-Uids (not x-scal-request-id) on the management config poll#6218delthas wants to merge 2 commits into
Conversation
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
|
❌ 1 Tests Failed:
View the full list of 2 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
Formatting-only commit: run Prettier on lib/management/poll.js, which was already prettier-dirty at the base commit, so the functional change on top stays prettier-clean and diff-minimal. Issue: CLDSRV-948
The management config-overlay poll emitted the werelogs req_id chain under the wrong header name. Rename the outgoing header from x-scal-request-id to x-scal-request-uids, matching cloudserver's own reader in lib/server.js. Also export loadRemoteOverlay and add a unit test asserting the header is sent. Issue: CLDSRV-948
7746fec to
f2ca340
Compare
benzekrimaha
left a comment
There was a problem hiding this comment.
LGTM.
side note and not blocking :
blobserver's lib/management/poll.js has the same x-scal-request-id header , we might need a follow up ticket
|
Re blobserver: it looks EOL (last real commit Feb 2021), so I don't think a follow-up is worth it. Let me know and I can create one as needed. |
The management config-overlay poll (
lib/management/poll.js,loadRemoteOverlay) sent the werelogsreq_idchain under the wrongheader name
x-scal-request-id. Rename the outgoing header tox-scal-request-uids, which matches cloudserver's own reader inlib/server.js. The value (log.getSerializedUids()) is unchanged.Pure rename: no dual-send. Also exports
loadRemoteOverlayand adds afocused unit test asserting the outgoing request carries
x-scal-request-uidsand notx-scal-request-id.Part of the OS-1089 reqUids-propagation audit. Note: the receiving
config/overlayendpoint on pensieve-api doesn't declare this header inits swagger params, but pensieve reads it via a global middleware
(
WithRequestId), so it applies to every endpoint regardless. Relatedpensieve-side reqUids work: PSVAPI-131.
Issue: CLDSRV-948