Skip to content

terraform-eventbridge-scheduled-lambda: Update runtime to python3.12 #2788

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

kakakakakku
Copy link
Contributor

Issue #, if available:
N/A

Description of changes:
Hi😀 Thanks for the useful patterns!

I updated the Lambda Python runtime version to python3.12.

While testing terraform-eventbridge-scheduled-lambda, I noticed that the Lambda runtime version python3.8 was deprecated. Although it's still deployable at the moment, it will not be allowed after October 1, 2025.
https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

To prevent future deployment issues, I updated the runtime to python3.12.
https://github.com/terraform-aws-modules/terraform-aws-lambda

Check

terraform apply completed successfully and works good.

Warning

Warning is likely caused by the fact that the AWS provider version is currently at v6 (due to >= 4.9 constraint), and data.aws_region.current.name is now a deprecated attribute. There is no functional impact at this time👍

╷
│ Warning: Deprecated attribute
│ 
│   on .terraform/modules/lambda_function/outputs.tf line 9, in output "lambda_function_arn_static":
│    9:   value       = local.create && var.create_function && !var.create_layer ? "arn:aws:lambda:${data.aws_region.current.name}:${data.aws_caller_identity.current.account_id}:function:${var.function_name}" : ""
│ 
│ The attribute "name" is deprecated. Refer to the provider documentation for details.
│ 
│ (and one more similar warning elsewhere)
╵
image

Thank you😀


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@@ -10,7 +10,6 @@ terraform {
}

provider "aws" {
profile = "default"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note: I think it’s better if the user can choose the profile to use😀 For example, I also referred to terraform-s3-lambda and terraform-lambda-sfn.

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

Successfully merging this pull request may close these issues.

3 participants