Comments (18)
@bradwood this is going to be fixed in the v4 beta coming out within the next week.
Any updates on this @Mmarzex -- it's been 3 weeks since this comment, but I'm not seeing v4 anywhere...
🙏 thank you
from serverless.
Same here. Also a bunch of AWS emails.
The upgrade to SLS v4 is simply impossible given the size of our infra in the time remained.
It would be great to have a 3.x.y patch release to fix this issue.
from serverless.
It's hard-coded in lib/plugins/aws/custom-resources/index.js - I guess that should be updated to nodejs18.x or nodejs20.x
from serverless.
Hi
Any updates on this one -- the AWS cutoff for node 16 is fast approaching.
from serverless.
@bradwood this is going to be fixed in the v4 beta coming out within the next week.
from serverless.
Got another bunch of emails from AWS about this yesterday.
@Mmarzex ? Is this going upgrade going to happen? Or do I need we need to solve this another way? Maybe just do a 3.x.y patch release, just to fix the runtime? And decouple it from all the v4 stuff?
Just a thought.
from serverless.
if we can't get rid of this lambda by the cut-off
@bradwood I think you can actually get rid of this lambda function.
If you set provider.logs.restApi: false
in serverless.(ts|yml|…)
the additional lambda function is not generated.
Don't know of the disadvantages of that approach though. I guess it has to do with the serverless dashboard, but I do not use that anyway
from serverless.
If you set
provider.logs.restApi: false
inserverless.(ts|yml|…)
the additional lambda function is not generated. Don't know of the disadvantages of that approach though. I guess it has to do with the serverless dashboard, but I do not use that anyway
This removes access logging for the API Gateway, which for many API's is a security requirement.
It's easy to manually enable though, so it would be an option as fallback if Serverless cannot support it.
from serverless.
any update on this?
from serverless.
Yes, making that change is working well, but the next version should address this problem.
The problem is that we cannot change that hard-coded value when we are deploying services through the pipeline and codebuild project.
from serverless.
I am also interested in this
from serverless.
Seeing how little time we have remaining (June 12), we have to look into alternatives already.
We can't exactly keep our fingers crossed we'll eventually get this resolved at this point, so I want to be sure we can still keep our applications going.
Maybe managing the custom resources ourselves through other IaC is an option?
Is there an easy way to see which resources were created as custom resource, or should we to go through each Lambda to see what they might've created?
from serverless.
@JaroVDH we are kinda at this point too - if we can't get rid of this lambda by the cut-off we're going to have to do some kinda hand-rolled alternative. I'm really not keen to go there, as unpicking what it does it likely to be PITA. But we are also up against it now. It's a pity that this issue has not had more focus from the Serverless team. :-/
from serverless.
@Mmarzex can you please let us know where we are with this?
from serverless.
FYI, June 12 won't end up killing any services with custom resources just yet.
https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html#runtimes-deprecated
Node.js 16:
Deprecation date: Jun 12, 2024
Block function create: Feb 28, 2025
Block function update: Mar 31, 2025
I will still be pushing to remove these custom resources from our deploys before the June deadline, but it's good to know that at least we won't be stuck because of it.
from serverless.
@JaroVDH thanks for this update. What about the idea of just releasing the runtime change as a 3.x.y release? Surely this is just a small change. Doing this takes all the pressure off waiting for v4 and keeps us all happy.
from serverless.
@JaroVDH thanks for this update. What about the idea of just releasing the runtime change as a 3.x.y release? Surely this is just a small change. Doing this takes all the pressure off waiting for v4 and keeps us all happy.
Sorry for the confusion, I'm not affiliated with Serverless Framework; I'm just another impacted user :)
from serverless.
Sorry for the confusion, I'm not affiliated with Serverless Framework; I'm just another impacted user :)
My bad -- apologies.
So I wonder if anyone who is part of the Serverless team is going to bother responding into this... It feels like we are just yelling into the abyss here... 😢
from serverless.
Related Issues (20)
- Detected unrecognized CLI options: "--d". HOT 1
- V4: serverless dev command does not work in eu-south-1 region. HOT 3
- V4: .env variables do not work in serverles.yml HOT 1
- V4: Default deploymentMethod 'direct' or 'changesets' HOT 3
- [v4] Unable to use basic cli functionality like help without aws credentials HOT 3
- Custom resource uses wrong datatype for version HOT 4
- existing:true S3 Bucket Still Tries to get deleted HOT 3
- `logs.restApi: true` fails to deploy HOT 10
- Serverless deploy not working HOT 1
- [Serverless V4] The "exclude" keyword doesn't work for esbuild HOT 4
- MIT License is a misnomer. The actual framework is closed-source and licensed.
- ESBuild plugin support (Serverless 4) HOT 4
- Bug with version 4.1.8 when trying to deploy HOT 3
- API Gateway Rest API V1 Access Logging creation HOT 3
- Does the S3 property under Provider section no longer create buckets anymore?
- Unable to Disable esbuild in Serverless 4.1.11 HOT 5
- Unable to bundle @aws-sdk in v4 HOT 4
- Recoverable error occurred (Socket connection timeout)
- [V4] Dev mode: handler not found in service directory HOT 1
- Unable to Enable "Helpers for Encryption in Transit" for Environment Variables in Python Lambda
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from serverless.