Lightning.Invocation.RequestHeaders (Lightning v2.19.0-pre)

Prepares inbound HTTP headers for storage in dataclip.request.

cookie and proxy-authorization are redacted by name; neither is addressed to a job. authorization and x-api-key -- the two headers LightningWeb.Auth reads -- keep their value with the trigger's own auth secrets scrubbed out of it, so a caller's token survives but the secret Lightning just consumed does not. Every other header is stored verbatim.

Summary

Functions

redact(req_headers, auth_methods)

Returns the map stored as dataclip.request["headers"].

Functions

redact(req_headers, auth_methods)

@spec redact([{String.t(), String.t()}], [Lightning.Workflows.WebhookAuthMethod.t()]) ::
  map()

Returns the map stored as dataclip.request["headers"].

auth_methods must be loaded: an unloaded association raises rather than being read as "no secrets to scrub". Duplicate header names collapse to the last, as Enum.into/2 did before this module existed.