Struct GcsStorage 

pub struct GcsStorage { /* private fields */ }

Available on crate features storage-azure or storage-gcs or storage-local or storage-s3 only.

Google Cloud Storage, through its JSON API and the outbound HTTP client (crate::http_client::Client) — no Google SDK.

Requests carry an OAuth 2.0 access token, found as Google’s client libraries find Application Default Credentials: RWS_GCS_ACCESS_TOKEN, then the file in GOOGLE_APPLICATION_CREDENTIALS (a service account key or authorized_user), then gcloud’s application_default_credentials.json, then the metadata server (Compute Engine, GKE Workload Identity, Cloud Run). Tokens are cached and refreshed before they expire. RWS_GCS_CREDENTIAL_SOURCE=token|file|metadata|none picks one; none sends no credentials (emulators).

Implementations

impl GcsStorage

pub fn new(config: GcsConfig) -> GcsStorage

pub fn from_env() -> Result<GcsStorage, StorageError>

Shortcut for GcsStorage::new(GcsConfig::from_env()?).

Trait Implementations

impl Storage for GcsStorage

fn url(&self, key: &str) -> String

{endpoint}/{bucket}/{key} — the object’s public URL (https://storage.googleapis.com/...), which works for objects readable by allUsers; private ones need a signed URL.

fn put( &self, key: &str, data: &[u8], content_type: &str, ) -> Result<String, StorageError>

Store data under key, overwriting any existing object at that key. Returns the key that was stored (backends that normalize or namespace keys may return a different string than the one passed in).

fn get(&self, key: &str) -> Result<Vec<u8>, StorageError>

Retrieve the bytes stored under key.

fn delete(&self, key: &str) -> Result<(), StorageError>

Delete the object stored under key. Backends generally treat deleting a missing key as a no-op success, matching S3’s semantics.

fn put_stream( &self, key: &str, reader: &mut dyn Read, content_type: &str, ) -> Result<String, StorageError>

Store everything reader yields under key — for a body too large to hold in memory, e.g. a streamed upload (Request::body read as a stream, #31). LocalStorage writes as it reads and S3Storage uploads in parts (S3 multipart upload), so memory stays at one part; the default reads everything first and calls Storage::put.