Harden transfers, auth, mounts, and releases#6
Merged
Conversation
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
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.
What changed
Why
The previous implementation could imply destructive
rclone syncbehavior, reported healthy status for some failed states, performed several multi-step mutations without full rollback, and lacked enough release, security, packaging, and failure-path verification for a data-management CLI.User impact
Normal syncs preserve destination-only files. Destructive mirroring is explicit and bounded. Authentication/session exports, mounts, persistent services, bootstrap installs, and machine-readable status now fail closed with actionable errors. Existing version-less sync configs and legacy state/vault names migrate safely.
Validation
go test ./...go test -race ./...go vet ./...mount_webdavmount/unmount