maximilien / maximilien/weave-cli
feat: Backup & Restore for Production Data
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 34
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Implement backup and restore capabilities for production vector database data.
Scope
- Implement Milvus backup to S3/GCS
- Add scheduled backup support
- Implement restore from backup command
- Add point-in-time recovery
- Test backup/restore workflow
Commands
weave stack backup
weave stack backup list
weave stack restore <backup-id>
Success Criteria
- Backup/restore works end-to-end
- Backup/restore guide complete
- Scheduled backups functional
Priority: Phase 2 - Week 2
Estimated: 1-2 days
Assignee: TBD
Related
Production feature - critical for data protection.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CLI entry points for weave stack backup, backup list, and restore <backup-id>, then inspect the existing vector-database integrations. The issue names no files or tests, so first map how Milvus and cloud storage are handled before defining the workflow. Done means end-to-end backup, restore, scheduling, point-in-time recovery, and the backup/restore guide are functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, gcp, go
- Domain
- cli, cloud, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100