api: fix WriteRawWithContext/PatchRawWithContext premature context cancel

[arashzjahangiri]

Summary

WriteRawWithContext and PatchRawWithContext both route through writeRaw, which installed a withConfiguredTimeout cancel and deferred it:

func (c *Logical) writeRaw(ctx context.Context, request *Request) (*Response, error) {
    ctx, cancelFunc := c.c.withConfiguredTimeout(ctx)
    defer cancelFunc()  // fires before caller reads resp.Body

    resp, err := c.c.rawRequestWithContext(ctx, request)
    return resp, err
}

The defer fires the moment writeRaw returns, cancelling the context the response body is bound to. For small responses the body is fully buffered before the cancel matters; for large responses still streaming at read time, the caller gets a spurious context canceled even though the request succeeded server-side.

This is the exact defect fixed for the read path in #18708 and is already absent from readRawWithDataWithContext and DeleteRawWithContext, both of which call RawRequestWithContext directly.

Fix

Remove withConfiguredTimeout/defer cancelFunc() from writeRaw and delegate to RawRequestWithContext directly — identical to the pattern already used by the read/delete raw paths:

func (c *Logical) writeRaw(ctx context.Context, request *Request) (*Response, error) {
    return c.c.RawRequestWithContext(ctx, request)
}

Callers who need a timeout can set one on the context they pass in (via context.WithTimeout or context.WithDeadline).

Also adds doc comments to WriteRaw, WriteRawWithContext, PatchRaw, and PatchRawWithContext noting that raw-response functions do not apply the client-configured timeout — consistent with existing comments on the read/delete raw variants.

Testing

Added TestWriteRawWithContextBodyReadable covering both WriteRawWithContext and PatchRawWithContext: starts a real test HTTP server, calls each method, and verifies the response body is fully readable after the call returns.

Fixes #31986

[vercel]

Deployment failed with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `public`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vault-ui	Error		Jun 29, 2026 10:46am

[hashicorp-cla-app]

All committers have signed the CLA.