Fix Lambda actionable EOL status#85
Merged
Merged
Conversation
Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019e8526-3375-7673-9279-3f1527b4b2bb
bakayolo
force-pushed
the
bena/fix-lambda-actionable-eol-status
branch
from
June 1, 2026 23:44
2f81d76 to
003fd84
Compare
nandiheath
approved these changes
Jun 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
eol_datemapping to the actionablesupportdate so past-support runtimes classify as REDdeprecated_support_endmapped to upstreameolso the later AWS terminal deprecated-support date remains available in the structuredeolblockWhy
A staging scan on current
origin/main(3c14919, snapshot74d2db30-df1f-442e-87ce-4f84baba0a7d) showed 4,172 Lambda resources moving RED → YELLOW compared with the v0.5.6 snapshot82dd88b4-33d3-4960-b0ce-0a3c4044fca3. The resource inventory was unchanged (28,294 resources, 0 added/removed); the drift was caused by #84 changing Lambdaeol_datefromsupportto upstreameol, making past-actionable-date runtimesdeprecated_support/YELLOW until AWS terminal support ends.Test plan
go test ./pkg/eol/endoflife ./pkg/config ./pkg/policy ./pkg/workflow/detection