Align 0.3.0 requirements with analyzer schema 3 - #16
Merged
Merged
Conversation
adit-chandra
changed the title
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.
The merged analyzer reports schema revision 3, but the 0.3.0 requirements target schema 2 and reject that image during publication. Target revision 3 from starting revisions 0, 1, and 2, retaining replay and configuration rotation at revision 3.
Keep exact capability validation, stop/migrate/start, and the AWS-first clean-install acceptance gate. Recovery requires a schema-3-compatible image or forward repair; preserving application data does not permit restarting an older analyzer. Regression coverage verifies publication rejects incompatible schema revisions and that supervised workloads use hosted repository selection without customer repository credentials.
Validation on the merged branch: 179 tests passed, 4 Kubernetes integration tests skipped locally; Ruff, formatting, package builds, and generated-schema consistency passed. GitHub CI is rerunning for the updated head, including both disposable-kind Kubernetes versions. The branch includes current main's manual-chart catalog mode, writable mirror storage, and CRD upgrade procedure.
After source review and merge, build the supervisor candidate from the resulting main SHA, then refresh the immutable catalog/inventory in #14. Its existing schema-2 candidate is obsolete and must not be used for the current customer installation.
Candidate inputs:
965d75670048ffede7b5e99f29accdbfe429c1f3; its image publication workflow passed.ghcr.io/promptless/pig-trace-analyzer@sha256:9bff062f8702c6efa6d72ced4ddb5aafc18861ee913ec0f18ff638f7cafa55a3. Anonymous manifest/config downloads and exact SHA-tag binding verified.a78be06deb18a7135751745d363feca6b6f5eb4e0d39fcf302ee48c964a83eb0.0.3.0. The supervisor digest awaits the merged-source build; real image capability execution and AWS acceptance must bind the complete candidate.