You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue occurs for me using wnx/sidecar-browsershot (which I know isn't this package), but having run through as much of the code as I can, it feels like this is a Sidecar thing.
Everything runs perfectly well in my local environment, however as soon as I run from our AWS staging environment I get the following error when trying to call it:
staging.ERROR: Function `browsershot` not found in environment `staging`.
It may exist other environments, you may need to overwrite the environment while deploying to `staging`.
See https://hammerstone.dev/sidecar/docs/main/functions/deploying#faking-the-environment for more information. {"userId":1,"exception":"[object] (Hammerstone\\Sidecar\\Exceptions\\FunctionNotFoundException(code: 0): Function `browsershot` not found in environment `staging`.
It may exist other environments, you may need to overwrite the environment while deploying to `staging`.
See https://hammerstone.dev/sidecar/docs/main/functions/deploying#faking-the-environment for more information. at /var/app/current/vendor/hammerstone/sidecar/src/Exceptions/FunctionNotFoundException.php:23)
[stacktrace]
#0 /var/app/current/vendor/hammerstone/sidecar/src/Manager.php(108): Hammerstone\\Sidecar\\Exceptions\\FunctionNotFoundException::make(Object(Wnx\\SidecarBrowsershot\\Functions\\BrowsershotFunction))
#1 /var/app/current/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(337): Hammerstone\\Sidecar\\Manager->execute(Object(Wnx\\SidecarBrowsershot\\Functions\\BrowsershotFunction), Array, false, 'RequestResponse')
...
The lambdas are there with the correct names, they have the exact same code in too.
Any thoughts or any more I can do to help diagnose the issue?
So I have managed to isolate the problem, and work around it. Just haven't dug in enough to understand why it's a problem and to see if it's a config issue in our staging environment.
The issue is in the nameWithPrefix() method in Hammerstone\Sidecar\LambdaFunction.
Problem
The issue occurs for me using wnx/sidecar-browsershot (which I know isn't this package), but having run through as much of the code as I can, it feels like this is a Sidecar thing.
Everything runs perfectly well in my local environment, however as soon as I run from our AWS staging environment I get the following error when trying to call it:
The lambdas are there with the correct names, they have the exact same code in too.
Any thoughts or any more I can do to help diagnose the issue?
Related issue:
stefanzweifel/sidecar-browsershot#89
The text was updated successfully, but these errors were encountered: