feat(hotfix,rollback): execute the per-component lifecycle in the harness and prove isolation - #528
Merged
Merged
Conversation
…ness and prove isolation The act and gitea harness can now trigger a named component's hotfix and rollback workflows and assert state.components.<name>.<env>. A new scenario runs a full hotfix and a rollback on one component and asserts the sibling's recorded state stays byte-unchanged across it, then mirrors the cycle, proving per-component lifecycle isolation end to end. Proving it surfaced and fixed two composition gaps: the hotfix plan never overlaid the component's recorded state, so a component-scoped plan failed with no recorded SHA (now overlays state.components.<name>.<env>, matching finalize and rollback); and the cherry-pick head branch was not component-scoped (now hotfix/<component>/<env>/<sha>, byte-identical single-component). Single-component behavior is byte-identical. Refs #293, #294, #296. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
joshua-temple
force-pushed
the
feat/lifecycle-e2e
branch
from
July 8, 2026 12:53
72f4764 to
6e0ccd2
Compare
This was referenced Jul 8, 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
1 participant
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.
Problem
Per-component hotfix and rollback runtime and generation are in place, but nothing proved they run in isolation end to end, and executing them surfaced composition gaps.
Fix
cascade-hotfix-<name>.yaml/cascade-rollback-<name>.yaml) and assertstate.components.<name>.<env>, reusing the component-scoped state assertion. Single-component steps unchanged.state.components.<name>.<env>into its working state, so a component-scopedhotfix planfailed with "no recorded state SHA" against a real multi-component manifest. It now overlays the component's recorded state, matching finalize and rollback.hotfix/<env>/<sha>(not component-scoped); nowhotfix/<component>/<env>/<sha>, byte-identical single-component, so two components hotfixing the same env and commit do not collide.Verification
go build ./...,go test ./...(2650 pass),golangci-lint run ./...clean; e2e build+vet clean; single-component byte-identical baseline gate green. New scenario54-component-hotfix-rollback-isolation.yamlruns a full hotfix and rollback on one component asserting the sibling's subtree stays byte-unchanged, then mirrors it. Passes locally in the act and gitea harness (61s); a single-component hotfix scenario also passes locally (no flake).Refs #293, #294, #296.