Suggestions to make lilmuckers deployment friendly

[raminv80]

Thanks for the module, I found it very useful and have some suggestions based on some problems I faced during deployment when I used the module with SQS.

First was regarding AWS permissions. In production, Ideal is not to give full access to AWS IAM users. Would you please highlight what are minimal required permissions on SQS to keep lilmuckers functional.

Next it would be highly appreciated to make name of queue and queue credentials configurable from admin. Magento doesn't have a good support for separating environments and it will make life much easier if environment specific variables like queue name and credentials could be set from admin.

Cheers

[lilmuckers]

Sorry for the delay in getting back to you (it's been a crazy few months :) )

The SQS support is fairly limited purely because I've never had to use SQS in anger (all my production releases have used beanstalkd or gearman.
I like to keep the queue configuration within the local.xml because the configuration in there is by its nature environment specific - plus changing the configuration mid cycle can cause you to lose queue tasks - so shouldn't be taken lightly. In my experience some things shouldn't be too easy :).
However when you get to granular queue permissions like you say, i can see why being able to add these on the fly would be valuable.

As an SQS user - do you have any suggestions as to a useful way to implement this kind of feature?

[peterjaap]

For deployment reasons, I'd suggest a fallback mechanism for the queue name & credentials. Preferably, those would be set through ENV variables set by the runner (i.e. Gitlab-ci runner or Bitbucket Pipelines runner). If those aren't present, it could look in a config system in the extensions' config like @raminv80 suggests.

As far as permissions go, from looking at the Amazon adapter, these are the methods used:

• changeMessageVisibility
• createQueue
• sendMessage
• receiveMessage
• deleteMessage

So the AWS permissions for those would be (see reference);

• sqs:ChangeMessageVisibility
• sqs:CreateQueue
• sqs:SendMessage
• sqs:ReceiveMessage
• sqs:DeleteMessage