This PR adds a more native queue handler. It tries to utilise as many internal Laravel components as possible, to stay as close to the other queue implementations as possible.

It's worth noticing that due to the way Lambda timeouts and SQS's integration with Lambda works, it's probably best to run with a batchSize of 1. If you want a larger batch size, make sure your jobs are designed in such a way that it won't break things if they are run more than once.

This package will add a timeout value (calculated for each job by subtracting a safety margin from the remaining invocation time) that will trigger a job timeout exception if the job is configured to do so.

Configuring a job to raise a failed exception on timeout can be done by adding the following to the job class:

public $failOnTimeout = true;

// or

public function shouldFailOnTimeout()
{
    return true;
}

When is this is set, the handler will catch the timeout, flag the job as failed and push it back onto the queue with it's attempts incremented with 1.

If the above is not set, the worker will not catch the timeout, and after SQS's visibility timeout expires, the job will be retried with the attempts NOT incremented.

Closes #6

Tested by hand using a test project deployed using sls.

Yesterday I had the pleasure of using this Laravel bridge for the first time, and the overall experience was very good. I only had a minor issue with the initial setup I got some chmod errors. The issue was regarding the logging which used the default Laravel settings. So I was curious if it could make sense to override the default logging setting to something more compatible with AWS such as stderr. I think this is something that is also done in the Briefs Laravel bridge, or maybe change the default path to /tmp instead of Laravel's default logging path. If you believe it is a good idea, I would like to make a PR.

Bref is doing something similar https://github.com/brefphp/laravel-bridge/blob/master/src/BrefServiceProvider.php#L58

Because content type could be application/x-www-form-urlencoded;charset=UTF-8.

It currently doesn't recognise the request as an url encoded form, and hence the form data is not available inside Laravel.

This should probably be fixed upstream as its also in Brefs PSR-7 bridge (which inspired this code).

Lastly, shouldn't we use something like https://symfony.com/doc/current/components/psr7.html#converting-objects-implementing-psr-7-interfaces-to-httpfoundation to convert the request from PSR-7 to Symfony instead?

Looks like Vapor does a full deployment and sets VAPOR_MAINTENANCE_MODE.

Let's see if we can set an environment variable without a full build, or re-use the last built package.

https://github.com/serverless/serverless/discussions/11089

The secrets injector and the storage directories helper, both write to stdout. This however doesn't work in PHP-FTP and results in a crash.

https://github.com/cachewerk/bref-laravel-bridge/blob/33c1fe09ce00d5c67bc20e1f4c9dad34f35e0ac0/src/Secrets.php#L37 https://github.com/cachewerk/bref-laravel-bridge/blob/33c1fe09ce00d5c67bc20e1f4c9dad34f35e0ac0/src/StorageDirectories.php#L31

Ideally we attempt to write to stderr, but wrapped in a try/catch block.

The package is quite opinionated, let's make it configurable.

• [x] Make ServeStaticAssets optional
• [x] Make ServeStaticAssets assets configurable
• [x] Document usage including the need for BREF_BINARY_RESPONSES
• [x] Make Log::shareContext() configurable

Let's focus on PostgreSQL, but why would ANYONE use something else.

PostgreSQL 9.6 upwards supports idle_in_transaction_session_timeout.

SET SESSION idle_in_transaction_session_timeout = '5min';

https://stackoverflow.com/a/41818410

It's fairly straight forward: https://github.com/laravel/vapor-core/blob/7ea7c0001795768a0fcb43d89524a7ac1cfef533/src/Runtime/Octane/Octane.php#L60-L125

This PR follows up on the following threads:

• https://github.com/brefphp/laravel-bridge/discussions/79#discussioncomment-4177668
• https://github.com/brefphp/laravel-bridge/discussions/79#discussioncomment-4177671

It changes the following:

• Add a default serverless.yml so that users can quickly get started without having to create it manually
• Switches to PHP-FPM by default (instead of Octane) so that all Laravel apps work out of the box (they don't have to be compatible with Octane)

Todo:

• [x] Add docs
• [x] Update changelog

How to get it to work:

• Add the required layer to your function(s)
• Ensure your functions have access to ssm:GetParameter
• Add APP_SSM_PREFIX and APP_SSM_PARAMETERS as usual

Minimal serverless.yml example:

service: my-app

provider:
  name: aws
  region: eu-central-1
  stage: staging
  runtime: provided.al2
  environment:
    APP_SSM_PREFIX: /${self:service}-${sls:stage}/
    APP_SSM_PARAMETERS: "APP_KEY, WORKERLESS_LICENSE_KEY, TEST_NON_EXISTING_KEY"
  iam:
    role:
      statements:
        - Effect: Allow
          Resource: arn:aws:ssm:${aws:region}:${aws:accountId}:parameter/${self:service}-${sls:stage}/*
          Action: [ ssm:GetParameter, ssm:GetParameters ] # singular for extension, plural for sdk

plugins:
  - ./vendor/bref/bref

functions:
  web:
    handler: php/runtime.php
    environment:
      APP_RUNTIME: octane
      BREF_LOOP_MAX: 250
    layers:
      - ${bref:layer.php-81}
      - arn:aws:lambda:eu-central-1:187925254637:layer:AWS-Parameters-and-Secrets-Lambda-Extension:2
    events:
      - httpApi: "*"

Encrypting secrets in a during artifact building and loading them from a file might be a better approach for scale. Requires PHP 8.1. Hat tip @GrahamCampbell.

https://github.com/GrahamCampbell/Envelope-Encryption