chore(synthetics): update runtimes#29446
Conversation
| * @deprecated Legacy runtime no longer supported by AWS Lambda. Migrate to the latest NodeJS Puppeteer runtime. | ||
| */ | ||
| public static readonly SYNTHETICS_NODEJS_PUPPETEER_1_0 = new Runtime('syn-1.0', RuntimeFamily.NODEJS); |
There was a problem hiding this comment.
I don't think we should add ones that are already deprecated. Can we remove these?
There was a problem hiding this comment.
My original thought for all these PRs was to have parity between the SDK and the CDK, as a starting off point for continuous, automatic checks. I can always ignore SDK versions/engines/runtimes etc. that are deprecated
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Issue # (if applicable)
Could not find any in the backlog
Reason for this change
Update the CDK listed Synthetics runtimes to match the current availability, as well as add missing deprecated versions
Description of changes
syn-1.0andsyn-nodejs-2.*were still namedSYNTHETICS_NODEJS_PUPPETEER_*{@link}tags to match the web documentationDescription of how you validated changes
I compared the current CDK versions to live SDK data, using the
synthetics:DescribeRuntimeVersionsAPI results. Deprecated versions were established using theDeprecationDatefieldChecklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license