Skip to content

fix(gcs): pass bucket_name to multistore GCS store#193

Merged
alukach merged 1 commit into
source-cooperative:mainfrom
alukach:worktree-gcs-bucket-name
Jul 22, 2026
Merged

fix(gcs): pass bucket_name to multistore GCS store#193
alukach merged 1 commit into
source-cooperative:mainfrom
alukach:worktree-gcs-bucket-name

Conversation

@alukach

@alukach alukach commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Problem

GCS-backed products 500 on every request in staging:

config error: failed to build GCS paginated store: Generic GCS error: Missing bucket name
status=500, s3_code=InternalError

The provider now resolves correctly (backend_type=gcs), but build_backend_options returned the gcs backend type with an empty options map — it never set bucket_name, which multistore's GCS store requires (bucket_name, service_account_key, skip_signature — see multistore types.rs). The s3 arm already inserts bucket_name from connection.details.bucket; the gcs arm was missing the equivalent line.

Fix

Mirror the s3 arm: insert bucket_name from details.bucket in the gcs arm.

Testing

  • cargo test (all native suites) + wasm build/clippy green via pre-commit hook.
  • Manual staging verification of a GCS list/HEAD recommended after deploy.

🤖 Generated with Claude Code

The GCS arm of build_backend_options resolved backend_type=gcs but never
inserted the `bucket_name` option, so multistore failed with
"config error: failed to build GCS paginated store: Missing bucket name"
(500 InternalError) on every request to a GCS-backed product.

Mirror the s3 arm: insert `bucket_name` from connection.details.bucket.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@alukach
alukach marked this pull request as ready for review July 22, 2026 22:51
@alukach
alukach merged commit 0efb66f into source-cooperative:main Jul 22, 2026
10 of 16 checks passed
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.

1 participant