Skip to content

AzureFilesystemAdapter

ListableFilesystemInterface over AzureBlobClient, against a fixed container.

Azure takes the container per call where S3 and GCS bind the bucket to the client, so the client is wrapped in an AzureBlobContainerClient that binds it. Everything after that, the path-to-key mapping, the error translation, container creation on first write, the listing, is the shared behaviour in ListableObjectStoreFilesystemAdapter and the container facade.

final readonly class AzureFilesystemAdapter extends ListableObjectStoreFilesystemAdapter

ExtendsListableObjectStoreFilesystemAdapter
SourceAzureFilesystemAdapter.php

public function __construct(AzureBlobClient $client, string $container, string $keyPrefix = ''): mixed

ParameterTypeDescription
$clientAzureBlobClient
$containerstring
$keyPrefixstring

Returns mixed

These come from an ancestor and are documented where they are declared.

MethodDeclared inDescription
delete()ObjectStoreFilesystemAdapterDeletes the object under $path.
exists()ObjectStoreFilesystemAdapterReports whether the store holds an object under $path.
lastModified()ObjectStoreFilesystemAdapterReturns the object’s modification time, taken from its Last-Modified metadata.
listContents()ListableObjectStoreFilesystemAdapter
read()ObjectStoreFilesystemAdapterReturns the body of the object stored under $path.
size()ObjectStoreFilesystemAdapterReturns the object’s size in bytes, taken from its Content-Length metadata.
write()ObjectStoreFilesystemAdapterStores $contents as the object under $path, replacing any existing object.