Repository navigation
docs(lmi): describe the lifecycle conformance design - #202
Open
zhongkechen wants to merge 10 commits into
Open
zhongkechen wants to merge 10 commits into
zhongkechen wants to merge 10 commits into
Conversation
Last of four stacked changes. SDK repositories call lmi-lifecycle.yml at a pinned commit and supply a stage script. The workflow owns the harness and cloud jobs, OIDC and account checks, credential refresh, timeouts, collection, cleanup, artifacts and summary. Its fixed concurrency group is the only cross-run guard; fork and Dependabot code stays on the unprivileged harness job. The suite guide and the README entry for the lmi-lifecycle command land here, once every part they describe exists.
- Dependabot code stays on the unprivileged runner for every event. The check sat inside the pull-request condition, so a Dependabot push selected the CodeBuild runner in the testing account. - Artifact names include the stack, runtime and region inputs, so one caller run can invoke the workflow more than once without the upload action rejecting a duplicate name. - The LMI guide shows the complete behavior budgets each requirement declares; the two-field example failed manifest validation. A new test ties the documented objects to the requirement catalog. The new regressions fail on the previous files.
…pr190-review-20261117
zhongkechen
marked this pull request as ready for review
November 19, 2026 21:16
zhongkechen
had a problem deploying
to
ai-pr-review-runtime
November 19, 2026 21:17 — with
GitHub Actions
Error
Contributor
Codex AI reviewNo actionable findings in this documentation-only PR. Read-only review completed without executing tests; live LMI acceptance remains an acknowledged validation gap. Reviewed commit |
This branch was successfully deployed
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
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.
Adds a design document for the Lambda Managed Instances lifecycle conformance suite. It explains the seven scenarios, the evidence contract, scheduling, AWS driver and SDK adapter responsibilities, retirement and recovery, and rollout.
Based on #199 and intended to follow it in stack #196. The document records the current live acceptance gap and the evidence issues tracked in #198 and #199.
Refs #161.
Validation on the docs commit used the workspace suite and coverage run (2,108 passed, 4 expected failures from #199), mypy, Ruff, YAML lint, distribution builds and wheel smoke checks, and Markdown rendering. Live LMI acceptance remains open.