Skip to content
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

Upgrade serverless to v3 #152

Closed
marchuffnagle opened this issue Sep 7, 2022 · 1 comment
Closed

Upgrade serverless to v3 #152

marchuffnagle opened this issue Sep 7, 2022 · 1 comment
Assignees
Milestone

Comments

@marchuffnagle
Copy link
Contributor

Cirrus is currently using serverless v1 for deployments: https://github.com/cirrus-geo/cirrus-geo/blob/main/src/cirrus/core/constants.py#L5

Serverless v1 and v2 default to using Node 12, which means that the custom resource lambdas that they deploy use Node 12 as well. This was fixed in Serverless, and is part of the 3.0.0 release.

Node 12 reached end-of-life on April 30, 2022. AWS has stated:

Starting November 14, 2022, Lambda will no longer apply security patches and other updates to the Node.js 12 runtime used by Lambda functions, and functions using Node.js 12 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Node.js 12 runtime. Starting December 14, 2022, you will no longer be able to update existing functions using the Node.js 12 runtime.

Cirrus needs to be updated to use serverless v3, or there's a risk that deployments will stop working in the next few months.

@jkeifer
Copy link
Collaborator

jkeifer commented Sep 8, 2022

This issue is effectively encapsulated in #139, as we need to support newer versions of serverless to support containerized lambdas, but calling it out explicitly as a separate issue is not a bad thing.

The work to support that issue and inherently serverless >=3.0.0 is already in the PR #150. As such I will add this issue to milestone 0.7.0 and ensure it is closed out when that PR is merged.

@jkeifer jkeifer self-assigned this Sep 8, 2022
@jkeifer jkeifer added this to the 0.7.0 milestone Sep 8, 2022
@jkeifer jkeifer mentioned this issue Sep 8, 2022
@jkeifer jkeifer closed this as completed Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants