-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to automatically truncate and uniquify long generated names #347
Comments
Thanks for reporting this issue @tomchiverton. The following exemple service file, using solely core serverless framework (not this plugin), results in the exact same error: # serverless.yml
service: myService
provider:
name: aws
runtime: nodejs14.x
functions:
myVeryVeryLongAndDefinitelyOverTheLimitOfSixtyFourCharsFunctionName:
handler: handler.index Could you let me know which trimming logic you're referring to ? On the other hand, the AWS CDK, used within Lift, to provision all non-Lambda function resources, does indeed handle resource name generation to guarantee those generated strings are within services constraints. Finally, you can use any property existing within Serverless framework documentation in the service: something-service
constructs:
pdf-email-send-queue-no-vpc:
type: queue
worker:
handler: pdfEmail.emailSender
name: short-name |
I think I was thinking of things like the S3 deploy bucket name being truncated. That work around is a handy trick. |
Description
In main Serverless, if a resource name ends up being too long, it's truncated and made unique e.g. 'my-long-name-trunc-H6E8'
Constructs do not appear fo this for their workers, so deployments of projects with "too long" service and/or stage and/or resource (
type: queue
) names fails.How to Reproduce
sls deploy --stage the-stage-name
Additional Information
The text was updated successfully, but these errors were encountered: