Download the PHP package pmg/sqs-transport without Composer
On this page you can find all versions of the php package pmg/sqs-transport. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pmg/sqs-transport
More information about pmg/sqs-transport
Files in pmg/sqs-transport
Package sqs-transport
Short Description A Symfony Messenger transport for SQS
License MIT
Informations about the package sqs-transport
SQS Symfony Messenger Transport
:warning: DEPRECATION NOTICE: This project is no longer maintained and might not work as expected. Use Alli Platform Bundle instead. Check this migration guide for more information: Migrating from PMG SQS Transport to Alli Platform Bundle
Installation
Bundle Usage
Add the PMG\SqsTransport\Bundle\PmgSqsTransportBundle to your application's
kernel. By default the transport bundle will use an aws.sqs service when
creating the transport factory and, by extension, the transport instances.
This service name is configurable, but it should place nice with the AWS
Bundle.
SqsClient Service Configuration
If you're not using the AwsBundle and would like to manually specify a service
that contains an instance of Aws\Sqs\SqsClient, some bundle configuration is
necessary.
Messenger Configuration
SQS Stamps
PMG\SqsTransport\Stamp\SqsReceiptHandleStamp: added when a message is received from SQS via thegetmethod. This allows the message to beacked orrejected later.PMG\SqsTransport\Stamp\SqsStringAttributeStamp: Allows you to add a custom message attribute. with aDataTypeset toStringand a string value.PMG\SqsTransport\Stamp\SqsNumberAttributeStamp: Allows you to add a custom message attribute. with aDataTypeset toNumberand a numeric value.
SQS Has a limit of 10 attributes per message, but the transport will
generally use at least one attribute to send the headers from the transport
serializer.
On Retries
The symfony messenger worker modifies an envelope with some retry metadata.
Since messages in SQS cannot be modified in place, we just put a new message
into the queue when that happens and the subsequent call to ack removes the
existing message.