Matt 02fc18f009 fix: Accept string instance_id in telemetry endpoint ...

The orchestrator sends instance_id as a string (e.g., "letsbe-orchestrator")
but the endpoint was expecting a UUID path parameter. This caused 422
validation errors when orchestrators tried to send telemetry.

- Changed path parameter from UUID to str
- Lookup instance by Instance.instance_id (string) instead of Instance.id (UUID)
- Store telemetry with instance.id (UUID) for correct FK relationship
- Updated TelemetryPayload schema to use str instead of UUID

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2025-12-24 15:11:30 +01:00

.gitea/workflows

ci: Add Gitea Actions workflow for Docker build

2025-12-22 14:12:12 +01:00

alembic

feat: Initial Hub implementation

2025-12-22 14:09:32 +01:00

app

fix: Accept string instance_id in telemetry endpoint

2025-12-24 15:11:30 +01:00

tests

feat: Initial Hub implementation

2025-12-22 14:09:32 +01:00

.env.example

feat: Initial Hub implementation

2025-12-22 14:09:32 +01:00

.gitignore

feat: Initial Hub implementation

2025-12-22 14:09:32 +01:00

alembic.ini

feat: Initial Hub implementation

2025-12-22 14:09:32 +01:00

CLAUDE.md

feat: Initial Hub implementation

2025-12-22 14:09:32 +01:00

docker-compose.yml

Use pre-built image from Gitea registry

2025-12-22 16:13:26 +01:00

Dockerfile

feat: Initial Hub implementation

2025-12-22 14:09:32 +01:00

hub.nginx.conf

Add nginx configuration for Hub deployment

2025-12-22 14:23:24 +01:00

requirements.txt

feat: Initial Hub implementation

2025-12-22 14:09:32 +01:00

Description

No description provided

786 KiB

Languages

TypeScript 99.6%

CSS 0.1%

Dockerfile 0.1%