For support requests please search or create posts on Serverless Forum: https://forum.serverless.com
carlosandrebp on master
upload email icon (compare)
carlosandrebp on master
Icons update (compare)
carlosandrebp on master
updates animations (compare)
andrepiresbp on master
Updates (compare)
andrepiresbp on master
Update (compare)
@/all
https://www.serverless.com/blog/introducing-serverless-cloud-public-preview
Let us know what you think!
BlobsResource:
Type: AWS::ApiGateway::Resource
Properties:
RestApiId:
Ref: ApiGatewayRestApi
ParentId:
Fn::GetAtt:
- ApiGatewayRestApi
- RootResourceId
PathPart: '{blob_id}'
when I change this Ref: ApiGatewayRestApi to Ref: blobs it says undefined blobs resource
aws
command line, but sls deploy
complains that the profile isn't configured. Are such role-based profiles supported by serverless
at all?
Hi am running into an issue where my env vars aren't being expanded when my cloud formation json is being created:
service: ${env:FOO, "foo-default"}${env:BAR, ""}
...
apiGateway:
name: ${env:FOO, "foo-default"}${env:BAR, ""}
...
provider:
stackName: ${self:service}
When I generate the cloud formation json it's creating these values:
"Export": {
"Name": "sls-${env:FOO, \"foo-default\"}${env:BAR, \"\"}-dev"
},
Basically It's treating the env vars as plain text. Should I report this as a bug or am I doing something wrong?
op@os-MacBook-Air resolute-serverless-backend % serverless
Serverless Error ----------------------------------------
Cannot reliably resolve "env" variables due to resolution conflict.
Environment variable "STAGE" which influences resolution of ".env" file were found to be defined in resolved ".env" file.DOTENV_ENV_VAR_RESOLUTION_CONFLICT
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com
Your Environment Information ---------------------------
Operating System: darwin
Node Version: 17.0.1
Framework Version: 2.66.1
Plugin Version: 5.5.1
SDK Version: 4.3.0
Components Version: 3.18.0
op@os-MacBook-Air resolute-serverless-backend % sls -v
Serverless: Running "serverless" installed locally (in service node_modules)
Framework Core: 2.66.1 (local)
Plugin: 5.5.1
SDK: 4.3.0
Components: 3.18.0
Hello. My typescript project with serverless component is giving the following error:
23s › Serverless › The operation cannot be performed at this time. An update is in progress for resource:...
I noticed that the error started to display without changing anything in the source code.
And doing some commit hash reversals, I noticed it's showing this message because my project is in typescript. If I revert the settings to be a javascript project, it works just fine.
can anyone help?
I've started running into an issue in which attempting to deploy produces this error:
Unzipped size must be smaller than 104060999 bytes
Part of the issue is the fact that serverless adds the full aws-sdk, along with all client libraries which totals 68MB. So I have the dynamodb client js code (plus dozens of others), even though I don't use it.
Is there a way to fix that? I need to reduce the size of my package
@elleryfamilia There is currently a bug with serverless
not tracking runtime dependencies correctly. A workaround is:
excludeDevDependencies: false
in serverless.ymlyarn install --prod
or equivalent for other package managersYou can then run serverless package
to see if a .zip
file in .serverless
became smaller
Hi guys, I'm trying to use functionResponseType
as specified here on serverless doc Setting the BatchSize but anything I've tried to doesn't worked, how can I return on my LambdaFunction a BatchResponse with only the failures messages like described on documentation.
Serverless example:
messageHandler:
tags:
event-type: queue
timeout: 10
handler: functions/handlers/messageHandler.handle
events:
- sqs:
arn:
Fn::GetAtt:
- MessagingQueue
- Arn
batchSize: 1000
maximumBatchingWindow: 30
functionResponseType: "ReportBatchItemFailures"
@atul.1055:matrix.org
https://www.serverless.com/framework/docs/providers/aws/events/streams
You need to add a stream event handler to your lambda
functions:
compute:
handler: handler.compute
events:
- stream:
type: dynamodb
arn:
Fn::GetAtt: [MyDynamoDbTable, StreamArn]
EMFILE: too many open files
.npx
but I don't understand how.Hi everyone, I am facing Serverless › ENOSPC: no space left on device, write
error when making a react deployment using npx serverless@2.64.1 deploy
More details here - actions/virtual-environments#4822. Any ideas on what exactly is the problem and a fix?