Download the PHP package quioteframework/cloud-azure without Composer
On this page you can find all versions of the php package quioteframework/cloud-azure. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download quioteframework/cloud-azure
More information about quioteframework/cloud-azure
Files in quioteframework/cloud-azure
Package cloud-azure
Short Description Minimal Azure Blob and Table Storage clients, Shared Key or Azure AD (workload identity / az login) authenticated REST access with no azure-sdk dependency, plus a signed-request method for operations they do not model themselves. Framework-agnostic (built on quioteframework/storage, not the Quiote framework itself) and usable outside a Quiote application; also shared by Quiote's own Azure session and filesystem backends.
License MIT
Homepage https://github.com/quioteframework/cloud-azure
Informations about the package cloud-azure
quioteframework/cloud-azure
Minimal Azure Storage clients for Quiote.
Quiote\Storage\Azure\AzureBlobClient: REST access to Blob Storage, Shared Key or Azure AD authenticated.Quiote\Storage\Azure\AzureTableClient: the same for Table Storage (Shared Key Lite only), which is a key/value store rather than object storage and is cheaper for small key/value-shaped payloads.
No microsoft/azure-storage-* dependency: these cover exactly the operations Quiote needs.
Bring your own PSR-18 HTTP client.
Install
You normally do not install this directly: quioteframework/session-azure and quioteframework/filesystem-azure both depend on it.
Use
AzureBlobClient takes an AzureCredential rather than a raw account key, so it never has to know how the request gets authorized:
auth selects the strategy:
shared_key(default): signs withaccount_key, the storage account's own key.workload_identity: exchanges the AKS workload identity webhook's projected service account token for a Storage-scoped Azure AD token. ReadsAZURE_TENANT_ID,AZURE_CLIENT_ID,AZURE_FEDERATED_TOKEN_FILEandAZURE_AUTHORITY_HOSTstraight from the environment; nothing to configure beyondauthitself.managed_identity: asks the Azure Instance Metadata Service (IMDS) for a token on behalf of whichever managed identity is attached to the node/pod. No configuration needed for a system-assigned identity; a user-assigned one needsclient_id.cli: reuses a developer'saz loginsession by shelling out toaz account get-access-token. For local development against a real storage account without ever handling an account key.chain: triesworkload_identity, thenmanaged_identity(skipped if a short reachability probe finds IMDS unreachable), falling back tocli. The one strategy that works unmodified both in-cluster and on a laptop.
No account key is ever read for workload_identity, managed_identity, cli or chain.
AzureBlobClient::listObjects() lists blobs in a container (List Blobs), and AzureBlobContainerClient::listObjects() does the same bound to one container. Both normalize pagination, prefix/delimiter grouping and per-entry metadata the same way S3Client and GcsClient do; see Quiote\Storage\ListableObjectStoreClientInterface.
License
MIT. See LICENSE.
All versions of cloud-azure with dependencies
quioteframework/storage Version ^4.0
psr/http-client Version ^1.0
psr/http-message Version ^2.0
psr/log Version ^3.0
nyholm/psr7 Version ^1.8