You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fde127d
Browse filesBrowse the repository at this point in the historyBrowse files
feat(reporting): add GCS, S3 and Azure Blob row providers (#1468)
* feat(reporting): add GCS, S3 and Azure Blob row providers
Adds the cloud providers for object row bindings (adcontextprotocol/adcp#7996,
section 3.4) as optional extras adcp[reporting-gcs], adcp[reporting-s3] and
adcp[reporting-azure]. Each takes official clients the host builds with its own
credentials and never imports the client library itself.
- GCS pins the object generation and writes with if_generation_match=0 and a
declared MD5. The probe requires uniform bucket-level access and enforced
public access prevention and refuses lifecycle Delete rules that can match live
objects under the binding prefix.
- S3 and S3-compatible stores need bucket versioning: the native version is the
write-unique VersionId, never the ETag, deletes confirm the exact version, and
the probe proves create-only behaviour empirically.
- Azure needs blob versioning: the native version is version_id, the probe
refuses public containers and stores that replace blobs.
- Every provider passes the shared provider conformance suite including
write-unique-version; S3 runs against moto with the real boto3 client.
Part of #1457.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* fix(reporting): carry the call budget into every provider SDK call
Threads the budget into every GCS and Azure call and refuses S3 clients without finite socket timeouts, since wait_for cannot stop a worker thread.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
0 commit comments