Add read-only deployed-cluster swap readiness - #53
Conversation
jglanz
left a comment
There was a problem hiding this comment.
you are recreating functionality with your readiness tool, the correct approach is to add new Steps and PhaseGroups to cluster-tool and then refactor your tool into FlowScenario(s) which already have reports, tooling and infrastructure; this approach would mean that running e2e-tests includes you hub readiness data and validation.
0136a2e to
2db8ce4
Compare
|
Refactor complete:
|
|
Status: swap readiness and exact outpost deployment-profile verification are implemented. This PR consumes wire-libraries-ts#56; its final frozen dependency update follows that SDK publication. Architecture: readiness stays read-only and uses the existing orchestration/Report system. It delegates ETH/SOL runtime identity checks to the SDK instead of duplicating verifier logic, keeps mutable endpoints separate from immutable deployment identity, and reports preflight readiness separately from a future funded transactional canary. Producers: Ethereum artifacts #176 · Solana artifacts #414 |
e16f086 to
879cd0e
Compare
|
Refactored into a FlowScenario here > #88 |
Summary
Adds a manual, read-only
wire-cluster-tool readinesspreflight for an already deployed Wire/Ethereum/Solana network group. It reuses existing Steps, PhaseGroups, Reports, and typed SDK clients; it is not wired into bootstrap, Hub, or CI.Verdicts
Current state
This remains a draft local operator tool. The branch is clean and fully pushed, but current
masterreconciliation has real conflicts in readiness CLI/docs/tests and was intentionally left for a focused follow-up. The current PR review and CI blockers remain unresolved.Run
Add
--outpost-deployment-profile-file <profile.json>only for the optional exact-deployment section.