Repository navigation
Retain and qualify final Linux agent package bytes - #25
Open
spenceralbrecht wants to merge 2 commits into
Open
spenceralbrecht wants to merge 2 commits into
spenceralbrecht wants to merge 2 commits into
Conversation
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.
Green fixture receipts do not retain a release package. Build one final Linux
vmpower-agent0.2.0 archive from the unmodified compiled bundle, then independently stat, hash and reopen its complete control/data contents immediately before installing those same bytes from each retained legacy package family.Keep every existing adverse phase, quarantine/BPF/cleanup control, Windows job and timeout. Only after both final-package lifecycle/report proofs, supervisor, cleanup and isolation pass, reopen the archive again and upload exactly the final deb plus its bounded provenance manifest with three-day retention. Fixture upgrade/crash variants and configuration are excluded.
Validation: 162 author tests, 79 independent focused tests and seven additional direct controls pass. Actual package construction, native deadline fit and artifact readback remain to be proved by this PR's configured native checks.
This prepares retained candidate bytes only. It creates no release tag, publishes no package, changes no customer agent and claims no post-success rollback or customer OS compatibility. Publication, an eligible pilot and safe recovery remain separate acceptance work.