- Create 06-00-SUMMARY.md with RED state confirmation (27 failing, 49 green) - Update STATE.md: progress 88%, decisions, session info - Update ROADMAP.md: phase 6 in progress (1/4 summaries) - Mark BACK-01 through BACK-04 complete in REQUIREMENTS.md
69 lines
2.7 KiB
Markdown
69 lines
2.7 KiB
Markdown
# Requirements: Ready2Blob
|
||
|
||
**Defined:** 2026-03-30
|
||
**Core Value:** An IT pro can go from zero to a deployable rclone setup in minutes — without needing to know rclone's config syntax or PowerShell deployment conventions.
|
||
|
||
## v1.1 Requirements
|
||
|
||
### Tech Debt
|
||
|
||
- [x] **TECH-01**: User sees only the script output blocks matching their selected deployment targets (Intune and/or RMM) in ReviewStep
|
||
- [x] **TECH-02**: User can navigate back from ReviewStep using an explicit Back button
|
||
- [x] **TECH-03**: Backend list in BackendSelectionStep is automatically derived from BACKEND_REGISTRY keys (no hardcoded list)
|
||
- [x] **TECH-04**: Dead `BackendFormValues<T>` export is removed from `src/schemas/index.ts`
|
||
- [x] **TECH-05**: BackendSelectionStep test suite runs without `act()` warnings
|
||
|
||
### Backends
|
||
|
||
- [x] **BACK-01**: User can configure an OneDrive remote (with OAuth token paste input and guidance)
|
||
- [x] **BACK-02**: User can configure an SFTP remote (host, user, password or key-based auth)
|
||
- [x] **BACK-03**: User can configure a Google Cloud Storage remote
|
||
- [x] **BACK-04**: User can configure a Backblaze B2 remote
|
||
|
||
### Validation
|
||
|
||
- [ ] **VALID-01**: User sees inline validation error when a field value violates backend-specific format rules (Azure account name: 3–24 lowercase alphanumeric; S3 region: valid format; etc.)
|
||
|
||
### UX
|
||
|
||
- [ ] **UX-01**: User can view a contextual tooltip on sensitive or complex fields (SAS token vs. access key, region codes, SFTP auth method, OneDrive token)
|
||
|
||
## Future Requirements
|
||
|
||
*(None identified — all backlog items are in scope for v1.1)*
|
||
|
||
## Out of Scope
|
||
|
||
| Feature | Reason |
|
||
|---------|--------|
|
||
| Multiple remotes in one config | Significant wizard UX complexity — defer to v2 |
|
||
| OAuth flow in browser (OneDrive) | Requires backend proxy; paste pre-obtained token instead |
|
||
| Test connection / credential validation | Requires backend proxy (CORS blocks direct cloud API calls) |
|
||
| RMM-named script variants | Generic SYSTEM-context script covers all RMM platforms |
|
||
| Save/load configurations | localStorage = credentials in browser storage = security risk |
|
||
|
||
## Traceability
|
||
|
||
| Requirement | Phase | Status |
|
||
|-------------|-------|--------|
|
||
| TECH-01 | Phase 5 | Complete |
|
||
| TECH-02 | Phase 5 | Complete |
|
||
| TECH-03 | Phase 5 | Complete |
|
||
| TECH-04 | Phase 5 | Complete |
|
||
| TECH-05 | Phase 5 | Complete |
|
||
| BACK-01 | Phase 6 | Complete |
|
||
| BACK-02 | Phase 6 | Complete |
|
||
| BACK-03 | Phase 6 | Complete |
|
||
| BACK-04 | Phase 6 | Complete |
|
||
| VALID-01 | Phase 7 | Pending |
|
||
| UX-01 | Phase 7 | Pending |
|
||
|
||
**Coverage:**
|
||
- v1.1 requirements: 11 total
|
||
- Mapped to phases: 11
|
||
- Unmapped: 0 ✓
|
||
|
||
---
|
||
*Requirements defined: 2026-03-30*
|
||
*Last updated: 2026-03-27 after roadmap creation — all 11 requirements mapped*
|