Skip to content

feat(gcs): Implement google gcp bucket provider - #1138

Open
vprashrex wants to merge 3 commits into
feat/google-gcp-credential-reg-and-providerfrom
feat/gcs-bucket-provider
Open

feat(gcs): Implement google gcp bucket provider#1138
vprashrex wants to merge 3 commits into
feat/google-gcp-credential-reg-and-providerfrom
feat/gcs-bucket-provider

Conversation

@vprashrex

@vprashrex vprashrex commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

Issue

Closes #PLEASE_TYPE_ISSUE_NUMBER

Summary

  • Before: The flow was not defined.
  • Now: A new GCS bucket provider has been implemented.
  • Required changes to integrate with the new storage solution.
  • Adjustments made for compatibility with existing infrastructure.

Checklist

Before submitting a pull request, please ensure that you mark these task.

  • Ran fastapi run --reload app/main.py or docker compose up in the repository root and test.
  • If you've fixed a bug or added code that is tested and has test cases.

Notes

Please add here if any other information is required for the reviewer.

Original PR description

Issue

Closes #PLEASE_TYPE_ISSUE_NUMBER

Summary

Explain the motivation for making this change. What existing problem does the pull request solve?

Checklist

Before submitting a pull request, please ensure that you mark these task.

  • Ran fastapi run --reload app/main.py or docker compose up in the repository root and test.
  • If you've fixed a bug or added code that is tested and has test cases.

Notes

Please add here if any other information is required for the reviewer.

- Added GCSBucketProvider for handling Google Cloud Storage (GCS) operations, including signed URL generation.
- Introduced GCSClient to manage GCS client instances with default bucket support.
- Created a global bucket-provider registry to resolve and manage different bucket providers.
- Implemented tests for GCS bucket provider functionality, including signed URL generation and credential handling.
- Enhanced attachment resolution to support GCS URIs, allowing for both native and signed URL handling based on provider type.
- Updated documentation to reflect changes in bucket provider architecture and functionality.
@coderabbitai

coderabbitai Bot commented Aug 19, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)
  • ready-for-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f727c7c-4598-44d5-9c88-3b503108cf9b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot changed the title Feat/gcs bucket provider feat(gcs): Implement new bucket provider Aug 19, 2026
@github-actions

Copy link
Copy Markdown

OpenAPI changes   🔴 6 breaking changes

Caution

Downstream consumers may need an update before merging.

Breaking changes  ·  6
Method Path Change
🔴 GET /api/v1/models added the new google-gcp enum value to the data/anyOf[subschema #1: ModelConfigListPublic]/data/items/provider response property for the response status 200
🔴 PATCH /api/v1/models added the new google-gcp enum value to the data/anyOf[subschema #1]/items/provider response property for the response status 200
🔴 POST /api/v1/models added the new google-gcp enum value to the data/anyOf[subschema #1]/items/provider response property for the response status 201
🔴 GET /api/v1/models/grouped added the new google-gcp enum value to the data/anyOf[subschema #1]/additionalProperties/items/provider response property for the response status 200
🔴 GET /api/v1/models/{provider}/{model_name} added the new google-gcp enum value to the data/anyOf[subschema #1: ModelConfigPublic]/provider response property for the response status 200
🔴 PATCH /api/v1/models/{provider}/{model_name} added the new google-gcp enum value to the data/anyOf[subschema #1: ModelConfigPublic]/provider response property for the response status 200
Full changelog  ·  21
Method Path Change
🔴 GET /api/v1/models added the new google-gcp enum value to the data/anyOf[subschema #1: ModelConfigListPublic]/data/items/provider response property for the response status 200
🔴 PATCH /api/v1/models added the new google-gcp enum value to the data/anyOf[subschema #1]/items/provider response property for the response status 200
🔴 POST /api/v1/models added the new google-gcp enum value to the data/anyOf[subschema #1]/items/provider response property for the response status 201
🔴 GET /api/v1/models/grouped added the new google-gcp enum value to the data/anyOf[subschema #1]/additionalProperties/items/provider response property for the response status 200
🔴 GET /api/v1/models/{provider}/{model_name} added the new google-gcp enum value to the data/anyOf[subschema #1: ModelConfigPublic]/provider response property for the response status 200
🔴 PATCH /api/v1/models/{provider}/{model_name} added the new google-gcp enum value to the data/anyOf[subschema #1: ModelConfigPublic]/provider response property for the response status 200
🟢 POST /api/v1/configs added the new google-gcp enum value to the request property config_blob/completion/anyOf[subschema #2: KaapiCompletionConfig]/provider/anyOf[subschema #1]/
🟢 POST /api/v1/configs added the new google-gcp-native enum value to the request property config_blob/completion/anyOf[subschema #1: NativeCompletionConfig]/provider
🟢 POST /api/v1/llm/call added the new google-gcp enum value to the request property config/blob/anyOf[subschema #1: ConfigBlob]/completion/anyOf[subschema #2: KaapiCompletionConfig]/provider/anyOf[subschema #1]/
🟢 POST /api/v1/llm/call added the new google-gcp-native enum value to the request property config/blob/anyOf[subschema #1: ConfigBlob]/completion/anyOf[subschema #1: NativeCompletionConfig]/provider
🟢 POST /api/v1/llm/chain added the new google-gcp enum value to the request property blocks/items/config/blob/anyOf[subschema #1: ConfigBlob]/completion/anyOf[subschema #2: KaapiCompletionConfig]/provider/anyOf[subschema #1]/
🟢 POST /api/v1/llm/chain added the new google-gcp-native enum value to the request property blocks/items/config/blob/anyOf[subschema #1: ConfigBlob]/completion/anyOf[subschema #1: NativeCompletionConfig]/provider
🟢 POST /api/v1/llm/chain/sts added the new google-gcp enum value to the request property stt_provider/anyOf[subschema #1]/
🟢 POST /api/v1/llm/chain/sts added the new google-gcp enum value to the request property tts_provider/anyOf[subschema #1]/
🟢 GET /api/v1/models added the enum value google-gcp to the property anyOf[subschema #1: Provider]/ of the query request parameter provider
🟢 PATCH /api/v1/models added the new google-gcp enum value to the request property items/provider
🟢 POST /api/v1/models added the new google-gcp enum value to the request property anyOf[subschema #1: ModelConfigCreate]/provider
🟢 POST /api/v1/models added the new google-gcp enum value to the request property anyOf[subschema #2]/items/provider
🟢 DELETE /api/v1/models/{provider}/{model_name} added the new enum value google-gcp to the path request parameter provider
🟢 GET /api/v1/models/{provider}/{model_name} added the new enum value google-gcp to the path request parameter provider
🟢 PATCH /api/v1/models/{provider}/{model_name} added the new enum value google-gcp to the path request parameter provider

main86e52020 · generated by oasdiff

@vprashrex
vprashrex changed the base branch from main to feat/google-gcp-credential-reg-and-provider August 19, 2026 05:18
@vprashrex vprashrex changed the title feat(gcs): Implement new bucket provider feat(gcs): Implement google gcp bucket provider Aug 19, 2026
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