feat: v1.3 Unraid Update Status Sync
Unraid GraphQL API foundation — connectivity, authentication, and
container ID format verified for native Unraid API integration.
Phase 14: Unraid API Access (2 plans, 4 tasks)
- Established Unraid GraphQL API connectivity via myunraid.net cloud relay
- Dual credential storage (.env.unraid-api + n8n env vars)
- Container ID format: {server_hash}:{container_hash} (128-char SHA256 pair)
- Complete API contract documented in ARCHITECTURE.md
- "unraid" test command added to Telegram bot
Phases 15-16 dropped (superseded by v1.4 Unraid API Native).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -76,3 +76,34 @@
|
||||
**Git range:** Initial commit → `e5c02f9`
|
||||
|
||||
---
|
||||
|
||||
## v1.3 Unraid Update Status Sync (Shipped: 2026-02-09)
|
||||
|
||||
**Delivered:** Unraid GraphQL API foundation — connectivity, authentication, and container ID format verified for native Unraid API integration.
|
||||
|
||||
**Phases completed:** 14 (1 phase, 2 plans) — Phases 15-16 dropped (superseded by v1.4 Unraid API Native)
|
||||
|
||||
**Key accomplishments:**
|
||||
- Established Unraid GraphQL API connectivity from n8n via myunraid.net cloud relay
|
||||
- Dual credential storage (.env.unraid-api + n8n env vars) mirroring existing patterns
|
||||
- Production-verified container ID format: `{server_hash}:{container_hash}` (128-char SHA256 pair)
|
||||
- Documented complete Unraid GraphQL API contract in ARCHITECTURE.md
|
||||
- Added "unraid" test command to Telegram bot for connectivity validation
|
||||
- Corrected schema documentation (isUpdateAvailable does not exist in Unraid 7.2)
|
||||
|
||||
**Stats:**
|
||||
- 23 files modified (+4,038/-2,213 lines)
|
||||
- 1 phase, 2 plans, 4 tasks
|
||||
- 19 commits
|
||||
- 1 day (2026-02-08)
|
||||
|
||||
**Git range:** v1.2 → `e4bd653`
|
||||
|
||||
**Descope note:** Original scope included Phases 15-16 (sync update status back to Unraid). These were dropped because v1.4 will replace the Docker socket proxy entirely with Unraid's GraphQL API — when Unraid IS the container management API, the badge sync problem solves itself.
|
||||
|
||||
**Tech debt accepted:** None — clean foundation for v1.4.
|
||||
|
||||
**What's next:** v1.4 Unraid API Native — replace Docker socket proxy with Unraid GraphQL API for all container operations.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user