This option is used together with BUCKET_STORAGE_MULTIPLE_ENDPOINTS to allow users to configure buckets in multiple bucket services, for instance to migrate from Google cloud bucket storage to a local service.

When BUCKET_STORAGE_MULTIPLE_ENDPOINTS is true, each bucket in global can have a separate endpoint configuration, which is defined in this GCP_ARCHIVING_ENDPOINT_BASE variable (e.g., http://my-own-s3:8080).

This allows an existing cluster running against Google Cloud storage to begin uploading segments to a self-hosted bucket storage by switching the endpoint base, while still keeping access to existing segments in Google Cloud storage.

See BUCKET_STORAGE_MULTIPLE_ENDPOINTS for more information.