Inquiry Regarding Node.js Version Inconsistency in Quota Monitoring Solution v6.3.1

[KadalurSupreeth]

Describe the bug

An inconsistency has been observed in the Node.js versions used in the latest release of Quota Monitoring Solution v6.3.1. All functions, except for the one listed below, are utilizing Node.js 22.x, while the following function is set to use Node.js 20.x:

Clarification is requested regarding whether this difference in Node.js versions is intentional. Is there a specific reason for retaining Node.js 20.x for this function, or will this be resolved in an upcoming update? The latest solution has already been deployed, and Node.js 20.x is expected to be unsupported early next year. Significant efforts to upgrade the solution are best avoided unless necessary.

To Reproduce

Function Name: QMListManagerQMListManagerProviderframeworkonEvent1F57B2C8
Description: AWS CDK resource provider framework - onEvent (quota-monitor-sq-spoke/QM-ListManager/QM-ListManager-Provider)
Code Snippet:
"Runtime": {
"Fn::FindInMap": [
"LatestNodeRuntimeMap",
{
"Ref": "AWS::Region"
},
"value"
]
}

"LatestNodeRuntimeMap": {
"af-south-1": {
"value": "nodejs20.x"
},
......

"us-east-1": {
"value": "nodejs20.x"
},

....
"us-west-2": {
"value": "nodejs20.x"
}
}

Expected behavior

Node.js versions should remain consistent unless differences are intentional.

Please complete the following information about the solution:

• Version: 6.3.1

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SOXXXX) - The AWS CloudFormation template for deployment of the AWS Solution. Version vx.y.z". You can also find the version from releases

• Region: [e.g. us-east-1]
• Was the solution modified from the version published on this repository?
• If the answer to the previous question was yes, are the changes available on GitHub?
• Have you checked your service quotas for the services this solution uses?
• Were there any errors in the CloudWatch Logs? How to enable debug mode?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
Add any other context about the problem here.

[abewub]

Thanks for the report. The solution is using the construct for a custom resource here. That constructor doesn't allow to specify the lambda run time version, so it takes whatever the default for the construct is. We will look into using a custom resource construct that allows to specify lambda versions in the next release. I added this to our backlog.

[KadalurSupreeth]

Thanks for the update. Can you please let me know the tentative next release date?

[abewub]

We don't have the timeline for the next release yet. I will update as soon as that is planned.

[andrisrovw]

Are there any news on this ? Is there any timeline planned for the next release or can this be done in a fix version of the current release ?

[abewub]

We don't have a timeline yet. But it will be addressed in time in our next release.