README

This project was forked due the retirement of the official Azure SDK. For more information visit Retirement notice: The Azure Storage PHP client libraries will be retired on 17 March 2024.

Features

Blobs
- create, list, and delete containers, work with container metadata and permissions, list blobs in container
- create block and page blobs (from a stream or a string), work with blob blocks and pages, delete blobs
- work with blob properties, metadata, leases, snapshot a blob
Tables
- create and delete tables
- create, query, insert, update, merge, and delete entities
- batch operations
Queues
- create, list, and delete queues, and work with queue metadata and properties
- create, get, peek, update, delete messages
Files
- create, list, and delete file shares and directories
- create, delete and download files

Please check details on API reference documents.

Minimum Requirements

PHP 8.0 or above
Required extension for PHP:
- fileinfo
- mbstring
- openssl
- xsl
- curl

Install via Composer

composer require azure-oss/storage

Usage

There are four basic steps that have to be performed before you can make a call to any Microsoft Azure Storage API when using the libraries.

First, include the autoloader script:

require_once "vendor/autoload.php";

Include the namespaces you are going to use.

To create any Microsoft Azure service client you need to use the rest proxy classes, such as BlobRestProxy class:

use MicrosoftAzure\Storage\Blob\BlobRestProxy;

To process exceptions you need:

use MicrosoftAzure\Storage\Common\ServiceException;

To instantiate the service client you will also need a valid connection string. The format is:

DefaultEndpointsProtocol=[http|https];AccountName=[yourAccount];AccountKey=[yourKey]

Or:

BlobEndpoint=myBlobEndpoint;QueueEndpoint=myQueueEndpoint;TableEndpoint=myTableEndpoint;FileEndpoint=myFileEndpoint;SharedAccessSignature=sasToken

Or if AAD authentication is used:

BlobEndpoint=myBlobEndpoint;QueueEndpoint=myQueueEndpoint;TableEndpoint=myTableEndpoint;FileEndpoint=myFileEndpoint;AccountName=[yourAccount]

Note that account name is required.

Instantiate a client object - a wrapper around the available calls for the given service.

$blobClient = BlobRestProxy::createBlobService($connectionString);
$tableClient = TableRestProxy::createTableService($connectionString);
$queueClient = QueueRestProxy::createQueueService($connectionString);
$fileClient = FileRestProxy::createFileService($connectionString);

Or for AAD authentication:

$blobClient = BlobRestProxy::createBlobServiceWithTokenCredential($token, $connectionString);
$queueClient = QueueRestProxy::createQueueServiceWithTokenCredential($token, $connectionString);

Note that Blob and Queue service supports AAD authentication.

Using Middlewares

To specify the middlewares, user have to create an array with middlewares and put it in the $requestOptions with key 'middlewares'. The sequence of the array will affect the sequence in which the middleware is invoked. The $requestOptions can usually be set in the options of an API call, such as MicrosoftAzure\Storage\Blob\Models\ListBlobOptions.

The user can push the middleware into the array with key 'middlewares' in services' $_options instead when creating them if the middleware is to be applied to each of the API call for a rest proxy. These middlewares will always be invoked after the middlewares in the $requestOptions. e.g.:

$tableClient = TableRestProxy::createTableService(
    $connectionString,
    $optionsWithMiddlewares
);

Each of the middleware should be either an instance of a sub-class that implements MicrosoftAzure\Storage\Common\Internal\IMiddleware, or a callable that follows the Guzzle middleware implementation convention.

User can create self-defined middleware that inherits from MicrosoftAzure\Storage\Common\Internal\Middlewares\MiddlewareBase.

Retrying failures

You can use bundled middlewares to retry requests in case they fail for some reason. First you create the middleware:

$retryMiddleware = RetryMiddlewareFactory::create(
    RetryMiddlewareFactory::GENERAL_RETRY_TYPE,  // Specifies the retry logic
    3,  // Number of retries
    1000,  // Interval
    RetryMiddlewareFactory::EXPONENTIAL_INTERVAL_ACCUMULATION,  // How to increase the wait interval
    true  // Whether to retry connection failures too, default false
);

Then you add the middleware when creating the service as explained above:

$optionsWithMiddlewares = [
    'middlewares' = [
        $retryMiddleware
    ],
];
$tableClient = TableRestProxy::createTableService(
    $connectionString,
    $optionsWithMiddlewares
);

Or by pushing it to the existing service:

$tableClient->pushMiddleware($retryMiddleware);

Following errors are not retried in current retry middleware:

Authentication failures.
"Resource Not Found" errors.
Guzzle request exceptions that does not bear an HTTP response, e.g. failed to open stream, or cURL Connection reset by peer, etc. Note: Community contribution to cover the Guzzle request exceptions are welcomed.

Retry types

RetryMiddlewareFactory::GENERAL_RETRY_TYPE - General type of logic that handles retry
RetryMiddlewareFactory::APPEND_BLOB_RETRY_TYPE * For the append blob retry only, currently the same as the general type

Interval accumulations

RetryMiddlewareFactory::LINEAR_INTERVAL_ACCUMULATION - The interval will be increased linearly, the nth retry will have a wait time equal to n * interval
RetryMiddlewareFactory::EXPONENTIAL_INTERVAL_ACCUMULATION - The interval will be increased exponentially, the nth retry will have a wait time equal to pow(2, n) * interval

Using proxies

To use proxies during HTTP requests, set system variable HTTP_PROXY and the proxy will be used.

Troubleshooting

Error: Unable to get local issuer certificate

cURL can't verify the validity of Microsoft certificate when trying to issue a request call to Azure Storage Services. You must configure cURL to use a certificate when issuing https requests by the following steps:

Download the cacert.pem file from cURL site.

Then either:

Open your php.ini file and add the following line:
```
curl.cainfo = "<absolute path to cacert.pem>"
```
OR

Point to the cacert in the options when creating the Relevant Proxy.

//example of creating the FileRestProxy
$options["http"] = ["verify" => "<absolute path to cacert.pem>"];
FileRestProxy::createFileService($connectionString, $options);

Code samples

You can find samples in the samples folder.

Contribute Code or Provide Feedback

You can find more details for contributing in the CONTRIBUTING.md.

If you encounter any bugs with the library please file an issue in the Issues section of the project.

azure-oss / storage

Maintainers

Details