For support requests please search or create posts on Serverless Forum: https://forum.serverless.com
Hello everybody, here I have a project with a lot of folders and files, so it's only natural that the imports become a little clutter.
I know that webpack offer solutions to add path aliases, and there is even separated packages which allow me to bring the same solution, but the main problem is that all of them expects that I have a main entry file, which I don't since I work with a lot of handlers.
Is there any other solution to this? Has anybody faced this same issue?
npm install -g serverless serverless-offline, but sls offline returns command not found. I have both packages in /usr/local/lib/node_modules...
I'm trying to enable or disable an event based on the stage, but having some difficulties. This is the code I've got:
custom:
scheduleEnabled:
prod: true
dev: false
functions:
functionName:
events:
-schedule:
rate: cron(.....)
enabled: ${self:custom.scheduleEnabled.${opt:stage, self:provider.stage}}Calling deploy with --stage prod, but the events are not being enabled in the Lambda Configuration Designer
Suggestion of 10 (TEN) crucial items for developing web application 2020
Could someone suggest the best tool/framework for small or medium size or enterprise web application for 2020 - 10 to 1000 users and millions of records
#1 - Best Unit test case framework
#2 - Best NoSQL Database
#3 - Best Relation Database
#4 - Best Synchronous Framework
#5 - Best Asychronous Framework
#6 - Best Front-End Framework (Active Development, Max Support)
#7 - Best Debugging Tool
#8 - Best Performance Tuning Tool
#9 - Best Code Coverage Tool
#10 - Best DB migration tool (ex: flyway)
Thanks.
sls invoke but sls offline is telling me that rust is unsupported as runtime. When changing to provided (and specifying --useDocker) I keep having the issue that it does't find the /var/task/bootstrap or /opt/bootstrap file. Even when specifying the handler.I am using
serverless-offline@next here.PS: awesome project - I try to introduce this in a company right now.
Heyo!
I'm getting the following error when deploying a project to AWS that defines an SQS queue which acts as the event source for a lambda function but where the defaultVisibilityTimeout is lower than the lambda timeout. I know that usually that's not something you want but in this particular case it's exactly what we want. The other problem is I don't always get it. I have another project with exactly the same setup which does deploy without problem. Is there anything you can think of that I might've missed that allows the one project the deploy but not the other?
"An error occurred: EventHandlerEventSourceMappingSQSSqs - Queue visibility timeout: 30 seconds is less than Function timeout: 900 seconds"
2 replies
config or configNumberTwo to the end of the lambda arn?
- Effect: "Allow"
Action:
- lambda:InvokeFunction
Resource:
- 'Fn::Join':
- ':'
-
- arn:aws:lambda
- Ref: 'AWS::Region'
- Ref: 'AWS::AccountId'
- function:${self:service}-${self:provider.stage}-${self:custom.functionName}
functions:
config:
warmup: true
handler: src/handler.config
configNumberTwo:
warmup: true
handler: src/handlerTwo.config
Hi! Please, clarify - is it possible to configure signalR using serverless framework with Azure Functions?
The thing is - in azure sdk it's possible to do, but not sure how to add a binding needed for signalR to the serverless.yml configuration file.
In Azure documentation the binding looks like this:
{
"type": "signalR",
"name": "signalRMessages",
"hubName": "log",
"direction": "out"
}But when I try to add to the serverless.yml:
SendMessage:
handler: SignalR_SendMessage/index.js
events:
- http: true
x-azure-settings:
route: /sendMessage
methods:
- POST
- OPTIONS
authLevel: anonymous
- signalR: <------------------this event
x-azure-settings:
name: signalRMessages
hubName: log
direction: outI keep getting Error "Binding signalR not supported" (but accordingly to azure docs signalR should be supported as well : https://docs.microsoft.com/en-us/azure/azure-functions/functions-triggers-bindings )
Thanks in advance!
An error occurred: clubhub-util-v1 - Export Clubhub-util-v1 cannot be updated as it is in use by clubhub-not-found-proxy-v1.How do i properly update stack without removing it and adding back on. Or is that the way it should be ?
Hi all, I am having an issue and I'm not quite sure how to resolve it. We are trying to add API Gateway REST API logs but running into an issue because of access permissions. We have developers setup so resources must be created in a specific path relating to their app. However, when we enable restApi logs, serverless tries to create a custom resource outside of the path.
ServerlessError: An error occurred: IamRoleCustomResourcesLambdaExecution - API:
iam:CreateRole User: arn:aws:iam::01234567890:user/username is not authorized to perform:
iam:CreateRole on resource: arn:aws:iam::01234567890:role/some-vars-IamRoleCustomResourcesLambdaExecution-AKQSB3EK46O7.We have tried to override the role as mentioned in the documentation but we can't overcome this error. We need to be able to direct serverless to create the role using the resource path we specify but can't figure out how to do that. Any help?
hello! I'm relatively new to serverless. Have been learning it the past month but don't have much production experience. A lot of clients I have are not using react but I'm building out react "widgets" that I'm embedding into their site.
I figured the best way to do this was to push the widgets to an s3 bucket with cloudfront. Does it make sense to server the widgets up as lambdas instead?
n3xtim3 Fine...
n3xtim3 Fat fingers 🤷♂️