Compatibility snapshot
The Blob Storage to Google Cloud profile supports block-blob CRUD and maps Azure ETag conditions to Cloud Storage generation behavior. Cloud Adapter retains lease state. Append blobs, page blobs, and tag queries are outside the profile. Direct Cloud Storage writers bypass adapter-held leases. Existing content, metadata, and lease state are not copied automatically.Prerequisites
- an installed Azure-origin Blob endpoint;
- a Blob Storage to Cloud Storage service adapter;
- an origin-side test credential;
- a Google Cloud runtime identity with access to one test bucket;
- a separate verification identity;
- Python 3 with
azure-storage-blobandgcloud.
Set values
Write through the Azure client
Verify Cloud Storage natively
Test error and concurrency behavior
Request a missing blob through the Azure client and retain its Azure error code, HTTP status, request ID, and diagnostic headers. If your application usesIf-Match or leases, add a test where one writer has stale state. Run every lease-dependent writer through Cloud Adapter.
Clean up
gcloud storage objects describe. Versioned or soft-delete-enabled targets can retain prior versions or recovery state; use an unversioned disposable target for this quickstart or remove the created version explicitly. Do not delete a shared bucket as part of object cleanup.