[Bug]: Lambda Python runtime 3.11

[lizdeika]

Terraform Core Version

1.5.4

AWS Provider Version

5.10

Affected Resource(s)

lambda compatible_runtimes does not support python 3.11

Announcement:
https://aws.amazon.com/about-aws/whats-new/2023/07/aws-lambda-python-3-11

It can be selected in AWS Console

Expected Behavior

to support python 3.11

Actual Behavior

Error: expected compatible_runtimes.0 to be one of [nodejs nodejs4.3 nodejs6.10 nodejs8.10 nodejs10.x nodejs12.x nodejs14.x nodejs16.x java8 java8.al2 java11 python2.7 python3.6 python3.7 python3.8 python3.9 dotnetcore1.0 dotnetcore2.0 dotnetcore2.1 dotnetcore3.1 dotnet6 nodejs4.3-edge go1.x ruby2.5 ruby2.7 provided provided.al2 nodejs18.x python3.10 java17 ruby3.2], got python3.11

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

Steps to Reproduce

Try to set lambda compatible_runtimes to python3.11

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[Oberon00]

Would it be possible to (optionally?) not "validate" the runtime at all and just pass the runtime string through as-is to AWS? This would make it possible to use/test new Lambda runtimes as soon as they are available without waiting for a terraform upgrade.

[g4-otayyan]

It's already fixed guys just needs to be released (which may be a couple of days I imagine)

[ewbankkit]

Relates #32726.
Closed via #32729.

[ascopes]

Is there a reason this is validated by the provider rather than left to be passed through to the AWS API like other "sentinel" string values elsewhere in the AWS provider API?

This would avoid a dependency on people using the newest AWS provider every time a new lambda runtime is released, and would remove the need to create new releases on the provider side as well.

Only downside I can think of from a consumer perspective is that plans wouldn't fail if the Lambda runtime was incorrect.

My concern is that for people with large codebases, it adds an urgency to having to constantly stay on the newest provider version for something that isn't bound to the AWS Provider itself, but rather the underlying API being consumed.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.