Chris LuandGitHub 9125b9c835 volume: extend the remote-endpoint guard to the azure backend (#10754) ...

* remote_storage/azure: allow a per-request HTTP client

Thread an optional *http.Client through NewAzBlobClient and add
azure.MakeWithHTTPClient, mirroring the S3 backend. When set, the client
overrides the azblob transport so a caller can pin the dial path. The
existing makers pass nil, so behavior is unchanged.

* volume: extend the remote-endpoint guard to the azure backend

The endpoint validation and rebinding-safe dialer in FetchAndWriteNeedle
covered the S3-SDK backends. The azure backend also dials a caller-supplied
AzureEndpoint, so route both families through a single guardedRemoteClient
helper that returns the endpoint each backend dials and a constructor bound
to the guarded HTTP client. azure is guarded only when AzureEndpoint is set;
an empty endpoint derives the public host from the account.
-volume.allowUntrustedRemoteEndpoints still opts out.

* rust volume: assert the azure endpoint has no remote-client path

The Rust volume server has no azure backend, so make_remote_storage_client
rejects the type before any client is built. Add a regression test pinning
that invariant.

2026-08-13 22:32:59 -07:00

..

azure

volume: extend the remote-endpoint guard to the azure backend (#10754)

2026-08-13 22:32:59 -07:00

gcs

remote storage: actually delete objects when a directory is removed (#10531)

2026-08-01 20:11:41 -07:00

s3

remote_storage: build all S3-compatible clients through one constructor (#10720)

2026-08-11 19:06:12 -07:00

remote_storage.go

read cold remote objects straight from the origin while caching (#10731)

2026-08-12 23:00:10 -07:00

track_sync_offset.go

chore: execute goimports to format the code (#7983)

2026-01-07 13:06:08 -08:00