- How do I install squigg/azure-queue-laravel?
- Install it with Composer using composer require squigg/azure-queue-laravel, then add an Azure Storage Queue connection in config/queue.php and configure your storage account credentials and endpoint. Once the connection is defined, dispatch and process jobs through Laravel's normal queue API. The package is a transport adapter, so it slots into Laravel's existing queue abstraction rather than introducing a separate job framework.
- Does squigg/azure-queue-laravel support Laravel 12?
- Yes. Version 12.0.0 is explicitly described as a Laravel 12.x compatibility release. The technical evaluation indicates PHP 8.2+ alongside Laravel 12.x, but you should confirm the exact constraints in the package composer.json before upgrading. If your application is still on Laravel 11, pin to v11 rather than forcing v12.
- Can I use Azure Storage Queues as a Laravel queue driver without Redis or SQS?
- Yes. squigg/azure-queue-laravel provides a Laravel queue driver backed by Azure Storage Queue, so you can dispatch and process jobs without operating Redis, RabbitMQ, or SQS. It is most compelling for Laravel applications already standardized on Azure. It is a transport adapter, not a job framework, so application code continues to use Laravel's queue API.
- How do I configure the Azure queue connection in config/queue.php?
- Add a new connection entry under the connections key in config/queue.php that uses this package's driver, then supply your Azure Storage account credentials and endpoint settings. Dispatch jobs by specifying that connection name or by setting it as your default queue connection. Keep an existing queue driver configured during rollout so you can switch back if smoke tests fail.
- Is v12 a breaking change from v11?
- Version 12.0.0 is a major version bump, but the available changelog only shows Laravel 12 compatibility and added GitHub Actions, with no explicit breaking-change list. That suggests the major bump is driven by framework constraint changes rather than new driver features, but it is still a risk. Review composer.json constraints, diff configuration keys against v11, and validate queue behavior in a non-production environment before upgrading.
- What Azure authentication methods are supported by this Laravel queue driver?
- The provided project context does not document the full set of supported Azure authentication methods, so verify this in the package README and source before relying on connection strings, SAS tokens, or managed identity. Authentication behavior is one of the key upgrade questions to confirm. Test your chosen credential method in staging, including rotation and expiry scenarios.
- How are visibility timeout, retries, and poison messages handled?
- These are important operational details to validate against the package's documentation and actual behavior. Laravel provides job-level retry and timeout configuration, while Azure Storage Queue has its own visibility timeout semantics that affect duplicate delivery and long-running jobs. Run representative success, retry, failure, timeout, and large-payload jobs in staging before production rollout.
- Can I run this package on Azure App Service, AKS, or Container Apps?
- Yes. The best fit is a Laravel 12 application running on Azure App Service, AKS, Container Apps, or VMs with network access to an Azure Storage account. Azure Storage Queue scales independently of your application workers, but Laravel worker concurrency, poll interval, visibility timeout, and job duration still determine throughput.
- How do I upgrade from v11 to v12 of squigg/azure-queue-laravel safely?
- Treat v12 as a framework-alignment upgrade: upgrade Laravel to 12.x first if needed, then update the package and your lockfile. Configure a staging Azure queue connection and run representative jobs covering success, retry, failure, timeout, and large payloads. Keep the previous queue driver available for rollback until production smoke tests pass.
- Is squigg/azure-queue-laravel actively maintained and safe for production?
- The package has a small maintainer set, and the addition of a GitHub Actions workflow is a positive maturity signal but does not eliminate single-maintainer or long-term support risk. Support is community-based via GitHub issues with no commercial SLA implied. Plan to track releases, document credential rotation, and test upgrades deliberately.