Skip to content

gcs: support custom GCS API endpoint via endpoint config option - #270

Open
HarnageaGabriel wants to merge 1 commit into
thanos-io:mainfrom
HarnageaGabriel:gcs-custom-endpoint
Open

gcs: support custom GCS API endpoint via endpoint config option#270
HarnageaGabriel wants to merge 1 commit into
thanos-io:mainfrom
HarnageaGabriel:gcs-custom-endpoint

Conversation

@HarnageaGabriel

Copy link
Copy Markdown

Summary

  • Adds an Endpoint field to gcs.Config, wired via option.WithEndpoint() for both the HTTP and gRPC client construction paths in providers/gcs/gcs.go.
  • Enables use of GCP regional endpoints, needed for compliance/latency reasons in some deployments.
  • Left empty by default (""), so existing behavior and default GCS endpoint resolution are unchanged — fully backward compatible.
  • Updated README GCS config docs and CHANGELOG.

Fixes thanos-io/thanos#7862.

Test plan

  • go build ./...
  • go test ./providers/gcs/... (11 passed, including new TestParseConfig_Endpoint)
  • go vet ./providers/gcs/...

Adds an Endpoint field to gcs.Config, wired via option.WithEndpoint()
for both the HTTP and gRPC client paths. Enables use of GCP regional
endpoints (https://cloud.google.com/storage/docs/regional-endpoints).
Left empty by default so behavior is unchanged.

For thanos-io/thanos#7862.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support setting endpoint for Google Cloud Storage (GCS) in Thanos

1 participant