A brief context of my use case - my application uses Scout Extended Laravel package and it has options for me to set env
SCOUT_QUEUE=true which it will send the index action to the queue and the queue is currently setup with AWS SQS t2.medium.
When I tried to run
php artisan scout:import on CI tool (Jenkins in this case), it behaves as expected that it will send the actions to the queue. The only issue I noticed is that my AWS SQS instance was having a hard time processing the job as I believe the index job is a little intensive to run and thus the instance became unresponsive.
Long story short, I am wondering when I run
php artisan scout:import, is it possible for me to tell if I want it to run on the spot and not pushing the job to the queue like passing a flag
--queue=false since my CI server is more capable of running intensive jobs and thus without having us to use a larger SQS instance for this use case?