fix(liquio): reconcile existing legacy token-only result safely #197
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "hex-73/liquio-legacy-result-reconcile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Minimal legacy token-only result Secret reconciliation, authored by Adrian Turnipseed. Mechanical cherry-pick of 4ab43c31a4d7c4319b40c58269a0de4ca2affbce onto fresh main
f5720a1a9a. Only the provisioner and its direct chart assertion change; both complete blobs match the independently reviewed candidate. No new implementation or leader technical review.Original independent source-only APPROVED: https://hex.local.samaschke.de/api/attachments/1ffd17d4-2504-4444-8669-3f86d6a9cd10/content (deleg_e68a062c / sa-0-0db80bc3). Reviewer exercised ten synthetic control-flow cases, not real SQL/jq/live behavior. Existing operator Helm/pytest receipt: four passed, three deselected, reused without repetition.
No workflow files exist at the canonical base, Actions workflows read returned 404; hosted CI is unavailable, not green. Existing branch rules require no status contexts or approvals. No policy changes or override.
Source merge is separate from selected chart pin promotion, regular provisioning and real Demo/Normal consumer acceptance. No credential resets, duplicate imports or blind retries.