Skip to content

chore: reconcile lambda runtime catalog - #282

Merged
ava-silver merged 7 commits into
prodfrom
ava.silver/chore/reconcile-lambda-runtime-catalog
Aug 25, 2026
Merged

ava-silver merged 7 commits into
prodfrom
ava.silver/chore/reconcile-lambda-runtime-catalog

Conversation

@ava-silver

@ava-silver ava-silver commented Aug 21, 2026 •

Copy link
Copy Markdown
Contributor

What does this PR do?

  • Uses the generated runtime catalog for exact, case-sensitive runtime resolution.
  • Retains nodejs14.x, nodejs16.x, and python3.7.
  • Removes nodejs12.x, python2.7, and python3.6.

Motivation

AWS blocks creation of functions with deprecated runtimes, but it still permits updates to existing functions that use them. Remote Instrumentation must continue to update functions using the retained runtimes while rejecting runtimes that no longer have supported compatibility layers.

Testing Guidelines

No manual validation.

Additional Notes

java8, java8.al2, provided.al2, and provided.al2023 retain their existing behavior.

Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@datadog-datadog-prod-us1

This comment has been minimized.

@ava-silver
ava-silver marked this pull request as ready for review August 21, 2026 21:09
@ava-silver
ava-silver requested a review from a team as a code owner August 21, 2026 21:09
Comment thread src/runtime-catalog.ts
@@ -0,0 +1,67 @@
// This file is generated. Do not edit it directly.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Does datadog-ci have this file too? Is it possible to import the one from there so we won't ever have to deal with mismatches on updates?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

good idea! i think the only thing would be that it would be a couple days behind, but thats a pretty reasonable approach

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

a couple caveats, the datadog-ci constant is not currently exported, and its shape differs from what Remote Instrumentation needs. Sharing it would require introducing a public package contract and coordinating a datadog-ci release and dependency upgrade. For this PR, I’m keeping the existing Remote Instrumentation boundary and replacing its local constants with centrally generated output. Both artifacts will be maintained from serverless-ci. I agree that exposing the effective supported-runtime contract from datadog-ci is a useful follow-up.

One caveat is that Remote Instrumentation’s runtime list currently differs from the effective support in its datadog-ci dependency. datadog-ci performs the final runtime validation, so Remote Instrumentation cannot successfully instrument every runtime listed in its local catalog today. We should align those contracts in a follow-up, ideally by exposing a supported-runtime contract from datadog-ci for Remote Instrumentation to consume.

@ava-silver
ava-silver merged commit 82df006 into prod Aug 25, 2026
8 checks passed
@ava-silver
ava-silver deleted the ava.silver/chore/reconcile-lambda-runtime-catalog branch August 25, 2026 20:24
@avangelillo avangelillo mentioned this pull request Oct 7, 2026
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