Storage path is somehow being reset to default

[damoncasale]

The storage path is somehow being reset to default, after the /tmp/storage paths are created. Help?

Here's my CloudWatch log:

<!--StartFragment-->
INIT_START Runtime Version: provided:al2.v75	Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:(obscured)
--
Creating storage directories: /tmp/storage/bootstrap/cache, /tmp/storage/framework/cache, /tmp/storage/framework/views, /tmp/storage/psysh
Running 'php artisan config:cache' to cache the Laravel configuration
INFO  Configuration cached successfully.
[23-Dec-2024 04:13:15] NOTICE: [pool default] 'user' directive is ignored when FPM is not running as root
[23-Dec-2024 04:13:15] NOTICE: fpm is running, pid 14
[23-Dec-2024 04:13:15] NOTICE: ready to handle connections
START RequestId: (obscured) Version: $LATEST
[2024-12-23 04:13:15] production.ERROR: The /var/task/bootstrap/cache directory must be present and writable. {"exception":"[object] (Exception(code: 0): The /var/task/bootstrap/cache directory must be present and writable. at /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php:179)
[stacktrace]
#0 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(132): Illuminate\\Foundation\\PackageManifest->write(Array)
#1 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(108): Illuminate\\Foundation\\PackageManifest->build()
#2 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(91): Illuminate\\Foundation\\PackageManifest->getManifest()
#3 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(80): Illuminate\\Foundation\\PackageManifest->config('aliases')
#4 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/RegisterFacades.php(26): Illuminate\\Foundation\\PackageManifest->aliases()
#5 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(316): Illuminate\\Foundation\\Bootstrap\\RegisterFacades->bootstrap(Object(Illuminate\\Foundation\\Application))
#6 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(187): Illuminate\\Foundation\\Application->bootstrapWith(Array)
#7 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(171): Illuminate\\Foundation\\Http\\Kernel->bootstrap()
#8 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(145): Illuminate\\Foundation\\Http\\Kernel->sendRequestThroughRouter(Object(Illuminate\\Http\\Request))
#9 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1190): Illuminate\\Foundation\\Http\\Kernel->handle(Object(Illuminate\\Http\\Request))
#10 /var/task/public/index.php(17): Illuminate\\Foundation\\Application->handleRequest(Object(Illuminate\\Http\\Request))
#11 {main}
"}
END RequestId: (obscured)
REPORT RequestId: (obscured)	Duration: 202.42 ms	Billed Duration: 1130 ms	Memory Size: 2048 MB	Max Memory Used: 97 MB	Init Duration: 926.59 ms

<!--EndFragment-->

I'm using serverless to deploy a Laravel 11 application from a Github action, and attempting to make a single API call to that application. Let me know what other information you need to debug this.

[mnapoli]

Can you provide more details: is this a brand new Bref and Laravel project? Or was it working before and stopped after upgrading? (if yes, upgrading what?)

Trying to understand if it is impacting everyone or related to something in your project that trips up the Laravel Bridge.

[damoncasale]

I've attempted to define a single API route which generates a PDF inside of a brand new Laravel 11 installation. It works fine in a local environment (running on an Amazon EC2 instance) but errors running on Lambda.

Since it's difficult to trace what parameters are being passed in Lambda, I logged the manifest path to a file in my local environment (by adding some logging code to the PackageManifest.php file itself). The manifest file isn't being written to the /tmp/storage folder, which is why this is erroring out.

I looked over the code for BrefServiceProvider.php and it looks like it's expecting the settings changes in the register hook to be preserved? I don't fully understand how that's supposed to happen.

Also, it looks like the Bref example is Laravel 10, not Laravel 11. Could Laravel 11 be causing an issue?

[FlorianRiquelme]

Having the same issue, worked around it by populating the bootstrap/cache folder with ./artisan config:cache in the pipeline step. This lambda runs once a day and i don't need to optimize for performance, that's why i initially skipped this step.

INIT_START Runtime Version: provided:al2.v75	Runtime Version ARN: arn:aws:lambda:eu-central-1::runtime:a0bd056330123245a9e6d9b44a8e84e33ef6569f70e6939e2c7bd4c19630a93b
--
Creating storage directories: /tmp/storage/bootstrap/cache, /tmp/storage/framework/cache, /tmp/storage/framework/views, /tmp/storage/psysh

It logs that it does create the directories at the correct path, however once the lambda actually starts executing it tries to write to /var/task/bootstrap/cache:

0c0c4594-f094-4992-b352-8e6ebd142ca8	Invoke Error	
{
    "errorType": "Bref\\ConsoleRuntime\\CommandFailed",
    "errorMessage": "[2025-01-31 15:32:45] staging.ERROR: The /var/task/bootstrap/cache directory must be present and writable. {\"exception\":\"[object] (Exception(code: 0): The /var/task/bootstrap/cache directory must be present and writable. at /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php:179)\n[stacktrace]\n#0 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(132): Illuminate\\\\Foundation\\\\PackageManifest->write(Array)\n#1 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(108): Illuminate\\\\Foundation\\\\PackageManifest->build()\n#2 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(91): Illuminate\\\\Foundation\\\\PackageManifest->getManifest()\n#3 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/PackageManifest.php(80): Illuminate\\\\Foundation\\\\PackageManifest->config('aliases')\n#4 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/RegisterFacades.php(26): Illuminate\\\\Foundation\\\\PackageManifest->aliases()\n#5 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(342): Illuminate\\\\Foundation\\\\Bootstrap\\\\RegisterFacades->bootstrap(Object(Illuminate\\\\Foundation\\\\Application))\n#6 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(474): Illuminate\\\\Foundation\\\\Application->bootstrapWith(Array)\n#7 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(196): Illuminate\\\\Foundation\\\\Console\\\\Kernel->bootstrap()\n#8 /var/task/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(1231): Illuminate\\\\Foundation\\\\Console\\\\Kernel->handle(Object(Symfony\\\\Component\\\\Console\\\\Input\\\\ArgvInput), Object(Symfony\\\\Component\\\\Console\\\\Output\\\\ConsoleOutput))\n#9 /var/task/artisan(13): Illuminate\\\\Foundation\\\\Application->handleCommand(Object(Symfony\\\\Component\\\\Console\\\\Input\\\\ArgvInput))\n#10 {main}\n\"} \n\nIn PackageManifest.php line 179:\n                                                                         \n  The /var/task/bootstrap/cache directory must be present and writable.  \n                                                                         \n\n",
    "stack": [
        "#0 /var/task/vendor/bref/bref/src/Runtime/Invoker.php(29): Bref\\ConsoleRuntime\\Main::Bref\\ConsoleRuntime\\{closure}('transfer:produc...', Object(Bref\\Context\\Context))",
        "#1 /var/task/vendor/bref/bref/src/Runtime/LambdaRuntime.php(94): Bref\\Runtime\\Invoker->invoke(Object(Closure), 'transfer:produc...', Object(Bref\\Context\\Context))",
        "#2 /var/task/vendor/bref/bref/src/ConsoleRuntime/Main.php(35): Bref\\Runtime\\LambdaRuntime->processNextEvent(Object(Closure))",
        "#3 /opt/bref/bootstrap.php(21): Bref\\ConsoleRuntime\\Main::run()",
        "#4 {main}"
    ]
}

Versions:
php -> 8.3
laravel -> 11.41.3
bref -> 2.4.5
bref/laravel-bridge -> 2.4.5
serverless -> 3.39.0

Deployed via serverless through gitlab:

service: some-service

provider:
  name: aws
  region: eu-central-1
  stage: ${opt:stage, 'staging'}
  environment:
    APP_ENV: ${self:provider.stage}
    SECRETS_MANAGER_SECRET_NAME: ${self:provider.stage}/${self:service}
    SNS_TOPIC_ARN: !Ref SomeServiceErrorTopic
  iamRoleStatements:
    - Effect: Allow
      Action:
        - 'secretsmanager:GetSecretValue'
      Resource:
        - arn:aws:secretsmanager:${self:provider.region}:*:secret:${self:provider.stage}/${self:service}
    - Effect: Allow
      Action:
        - 'sns:Publish'
      Resource:
        - !Ref SomeServiceErrorTopic

plugins:
  - ./vendor/bref/bref
  - serverless-plugin-aws-alerts

custom:
  alerts:
    stages:
      - production
      - staging
    dashboards: true
    topics:
      ok: ${self:service}-${opt:stage}-alerts-ok
      alarm: ${self:service}-${opt:stage}-alerts-alarm
    alarms:
      - functionThrottles
      - functionErrors
      - functionDuration
      - functionInvocations
functions:

  artisan:
    handler: artisan
    runtime: php-83-console
    timeout: 720 # in seconds
    events:
        - schedule:
              rate: rate(24 hours)
              input: '"artisan:command"'

package:
  patterns:
    - '!node_modules/**'
    - '!public/storage'
    - '!resources/assets/**'
    - '!storage/**'
    - '!tests/**'
    - '!database/*.sqlite'
    - '!.ddev/**'
    - '!node_modules/**'

resources:
  Resources:
    SomeServiceErrorTopic:
      Type: AWS::SNS::Topic
      Properties:
        DisplayName: Some Service Error Topic
        TopicName: ${self:service}-${self:provider.stage}-error-topic

[mnapoli]

I stumbled upon that error after accidentally adding '!bootstrap/cache/**' to the excluded patterns.

This was a mistake. I believe that what happens is that Laravel needs at least:

bootstrap/cache/packages.php
bootstrap/cache/services.php

to boot up (and then the Bref service provider can adjust the cache location).

These files are created (I believe) after composer install runs, in post-install scripts. So I think it would be fair to expect that these files always exist. If they don't, it means you need to run composer install.

Let's keep this issue open to see if others run into the problem. If you do, please detail why bootstrap/cache is deployed empty: is there a reason for that?