Skip to content

fix: bind prepared provider identity and redact diagnostics - #112

Merged
jethac merged 6 commits into
mainfrom
fix/cloud-prepared-volume-identity-privacy
Sep 4, 2026
Merged

jethac merged 6 commits into
mainfrom
fix/cloud-prepared-volume-identity-privacy

Conversation

@jethac

@jethac jethac commented Sep 4, 2026

Copy link
Copy Markdown
Member

Summary

  • Bind prepared storage readiness and plan candidates to the stable local registry identity plus the exact provider volume identity and storage facts.
  • Revalidate the bound storage identity before first submit and preserve the binding through dispatch, replay, and restart paths.
  • Redact private local/provider storage identifiers and related authority data from public prepared-volume diagnostics.

Validation

  • python -m pytest -q — 1101 passed, 6 skipped.
  • Base is main; accepted implementation head is the pushed branch tip.
  • No provider, BWS, RunPod, or paid-resource operations were performed.

Safety

  • Prepared and cold/ephemeral paths retain their existing behavior.
  • Mismatched, replaced, missing, or drifted storage authority rejects atomically before job/event/lease/provider mutation.
  • Public preflight responses use fixed safe wording and do not serialize private storage identifiers.

@jethac
jethac merged commit 38e46f3 into main Sep 4, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant