fix(s3): 404 satisfies fs.ErrNotExist — unblocks the #153 migration boot #163
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/s3-notexist"
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?
The v0.5.2 dogfood deploy crashlooped:
MigrateFileprobing the empty bucket got the s3 driver'sstorage.ErrNotFound(notfs.ErrNotExist) and treated first-boot as a hard error — exactly the breadcrumb #152/#153 recorded and the deploy verified the hard way. Fix at the source: the driver's 404 mapping now returnserrors.Join(storage.ErrNotFound, fs.ErrNotExist), so existing sentinel callers keep matching and every posix-parity caller (statestore included) can test not-exist uniformly. Migration never ran, so no partial state: PVC files intact, clean refusal as designed.