Skip to content

Expose structured EOL lifecycle data#84

Merged
bakayolo merged 1 commit into
mainfrom
bena/eol-lifecycle-blocks
Jun 1, 2026
Merged

Expose structured EOL lifecycle data#84
bakayolo merged 1 commit into
mainfrom
bena/eol-lifecycle-blocks

Conversation

@bakayolo

@bakayolo bakayolo commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • replace snapshot EOLDate JSON with a structured eol block
  • include standard support, deprecated/security support, extended support, terminal EOL, and actionable_date
  • use the first future lifecycle boundary for yellow warning windows while still preserving later dates
  • add declarative deprecated_support_end / deprecated_support support and update Lambda lifecycle mapping

Why

Some products expose multiple relevant lifecycle dates. RDS MySQL now needs both minor-version standard-support dates and later major/extended support dates. The collector should preserve all available lifecycle dates, but only warn early on the first actionable boundary.

Validation

  • go test ./pkg/types ./pkg/eol/endoflife ./pkg/policy ./pkg/workflow/detection ./pkg/snapshot
  • go test ./pkg/config

@bakayolo
bakayolo requested a review from a team as a code owner June 1, 2026 20:38
@bakayolo
bakayolo force-pushed the bena/eol-lifecycle-blocks branch from e183ff1 to 8c23827 Compare June 1, 2026 21:07
@bakayolo
bakayolo merged commit 3c14919 into main Jun 1, 2026
7 checks passed
@bakayolo
bakayolo deleted the bena/eol-lifecycle-blocks branch June 1, 2026 22:22
bakayolo added a commit that referenced this pull request Jun 1, 2026
## Summary
- restore Lambda `eol_date` mapping to the actionable `support` date so
past-support runtimes classify as RED
- keep `deprecated_support_end` mapped to upstream `eol` so the later
AWS terminal deprecated-support date remains available in the structured
`eol` block
- update adapter tests and docs to lock the intended Lambda semantics

## Why
A staging scan on current `origin/main` (`3c14919`, snapshot
`74d2db30-df1f-442e-87ce-4f84baba0a7d`) showed 4,172 Lambda resources
moving RED → YELLOW compared with the v0.5.6 snapshot
`82dd88b4-33d3-4960-b0ce-0a3c4044fca3`. The resource inventory was
unchanged (28,294 resources, 0 added/removed); the drift was caused by
#84 changing Lambda `eol_date` from `support` to upstream `eol`, making
past-actionable-date runtimes `deprecated_support`/YELLOW until AWS
terminal support ends.

## Test plan
- `go test ./pkg/eol/endoflife ./pkg/config ./pkg/policy
./pkg/workflow/detection`

Co-authored-by: Amp <amp@ampcode.com>
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.

2 participants