This release is a pre-release and may not be stable for production use.
storage-kernel-provider-gcp-storage
GCP Cloud Storage provider for Storage Kernel.
This provider maps StorageLocation.bucket to a Cloud Storage bucket and
StorageLocation.prefix to an object-name namespace.
Install
uv add storage-kernel-contracts storage-kernel-provider-gcp-storage
Usage
from storage_kernel.contracts import StorageClientOptions, StorageLocation
from storage_kernel.provider_gcp_storage import (
GcpStorageProviderOptions,
create_gcp_storage_client,
)
storage = create_gcp_storage_client(
StorageClientOptions(location=StorageLocation(bucket="my-bucket", prefix="prod")),
GcpStorageProviderOptions(project_id="my-project"),
)
await storage.send_content("docs/readme.txt", "Hello")
The provider uses google-cloud-storage behind the provider boundary. When
credentials and client are omitted, authentication follows Google
Application Default Credentials. An injected client is caller-owned and may be
used for custom SDK configuration or tests.
Provider Options
| Option | Purpose |
|---|---|
project_id |
GCP project used by the SDK factory |
credentials |
Explicit credentials dictionary passed to the SDK factory |
public_base_url |
Optional CDN/custom base URL for get_public_url |
client |
Optional caller-owned Google Storage client |
Capabilities
- full binary and text reads/writes
- blob read streams
- resumable writable upload streams
- prefix-based directory listing and recursive deletion
- same-provider native copy
- Cloud Storage signed URLs
- public URLs through
public_base_urlor the blob public URL
Provider SDK errors are normalized into Storage Kernel errors such as path not found, permission denied and provider error.
Metadata
Release files for storage-kernel-provider-gcp-storage 0.1.0a7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| storage_kernel_provider_gcp_storage-0.1.0a7.tar.gz | 8.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| storage_kernel_provider_gcp_storage-0.1.0a7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.3 kB
Release files / storage_kernel_provider_gcp_storage-0.1.0a7.tar.gz
| Download URL | storage_kernel_provider_gcp_storage-0.1.0a7.tar.gz |
|---|---|
| Size | 8.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
619cbb09492c8103a3ad7db8b1f6f1d0e999b8f7df8016eeac28d5e15f9a3c75
|
|
BLAKE2b-256 checksum How to use checksums |
c647a00e7c0fdef206c95009d79092e22d8d480f5ee42ee3264aed6918e672c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Release files / storage_kernel_provider_gcp_storage-0.1.0a7-py3-none-any.whl
| Download URL | storage_kernel_provider_gcp_storage-0.1.0a7-py3-none-any.whl |
|---|---|
| Size | 11.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ce60f0b5332bd5d5fc2ea6b5820161770a3a855c3f04e29f11567771c935f2cc
|
|
BLAKE2b-256 checksum How to use checksums |
330d51545650a5abcfbbb9b17b94b46292fdde4cc1c9ffc3575affe4ec078dbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Security for storage-kernel-provider-gcp-storage 0.1.0a7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.