gcp_gcs

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

### Added
- **Resumable uploads** — `start_resumable_upload/3` accepts an `:origin`
  option, forwarded as the `Origin` header on the session-initiation POST.
  Required for browser-based resumable uploads (server initiates the session,
  browser PUTs the bytes): GCS only returns CORS headers on requests to the
  session URI when the session was initiated with an `Origin` — the bucket's
  CORS configuration alone does not apply to session URIs. Opt-in and
  backwards-compatible; mirrors `origin` in Google's official clients
  (google-cloud-node's `createResumableUpload`, google-cloud-python's
  `Blob.create_resumable_upload_session`). The `fake-gcs-server` emulator does
  not enforce CORS, so this is covered by `Bypass`-based tests asserting the
  exact headers sent.

## [0.2.0] - 2026-07-07

### Changed
- Use Elixir's built-in `JSON` module (Elixir 1.18+) for encoding/decoding
  instead of `Jason`, and drop the `jason` dependency.

### Fixed
- **Resumable uploads** — send an explicit `Content-Length` on both resumable
  requests so real GCS no longer rejects them with `411 Length Required`: `0`
  on the bodyless session-initiation POST, and the known file size on the
  session PUT (which also stops Mint from falling back to
  `transfer-encoding: chunked` for the stream body). The `fake-gcs-server`
  emulator does not enforce this, so the failure only appeared against the
  live API. Regression covered by a `Bypass`-based test that asserts the exact
  headers sent.

## [0.1.0] - 2026-06-25

Initial release.

### Added
- **Buckets** — `create_bucket/3`, `get_bucket/2`, `list_buckets/2`,
  `delete_bucket/2`, `update_bucket/3`
- **Object metadata** — `get_object/3`, `list_objects/2` (with `prefix`/`delimiter`
  paging), `delete_object/3`, `update_object/4`, `copy_object/5`,
  `compose_object/4`, `rewrite_object/5` (token-following), `move_object/4`
- **Uploads** — `put_object/4` (simple), `upload_file/4` and `upload_stream/4`
  (resumable, constant memory), `upload/4` (auto-selects strategy), plus the
  low-level `start_resumable_upload/3` and `upload_chunk/3` primitives
- **Downloads** — `download/3` (buffered), `download_to_file/4` and
  `download_stream/5` (streamed, constant memory)
- **`GcpGcs.Error`** — structured error type with `code`, `message`, `details`,
  and HTTP `status`; HTTP statuses mapped to canonical atoms
- **`GcpGcs.Auth`** — OAuth2 access tokens via Goth or the gcloud CLI, with
  ETS-backed caching; auth is skipped automatically in emulator mode
- **`GcpGcs.Telemetry`** — `[:gcp_gcs, :request, _]` and `[:gcp_gcs, :auth, _]`
  span events
- **`GcpGcs.Config`** — production/emulator endpoint resolution, including the
  `STORAGE_EMULATOR_HOST` environment variable, and Finch pool configuration
- Input validation for bucket names, object names, project IDs, and source
  object lists, returning `{:error, %GcpGcs.Error{code: :validation_error}}`
- `docker-compose.yml` for a local `fake-gcs-server` emulator and an
  integration test suite (run with `mix test --include integration`)