You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(vault-secrets): use @adobe/fetch Response to restore .raw() compatibility
The error response returned on Vault failure used the native Node.js
`new Response()` which produces native Web API Headers. Those headers
lack the `.raw()` method that `helix-universal`'s `aws-adapter.js`
calls unconditionally on every response.
When the dev Vault egress was blocked (403), every Lambda invocation
hit the vault error handler, returned a native Response, and crashed
in the adapter with `response.headers.raw is not a function` —
surfaced as HTTP 500 on all API endpoints.
Fix: import Response from `@adobe/fetch` (already a declared
dependency). Its Headers class implements `.raw()`, making it
compatible with the helix-universal adapter.
Added regression tests that assert `.raw()` is callable on the 502
error response, covering bootstrap failure, Vault 403, and secret
read failure scenarios.
Made-with: Cursor
0 commit comments