-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Description
User Request
Implement the Threads messaging service end-to-end:
- Implement the gRPC service in
agynio/threadsbased on the proto published inagynio/api(PR #23, merged) - Set up CI and release workflows, publish first version
- Add the service to
agynio/bootstrap_v2
Architecture Reference
- Architecture doc:
agynio/architecture→architecture/threads.md - Proto schema:
agynio/api→proto/agynio/api/threads/v1/threads.proto - New service guide:
architecture/operations/new-service.md - CI/CD guide:
architecture/operations/ci-cd.md
Implementation Specification
Full spec prepared by researcher at /workspace/THREADS_IMPLEMENTATION_SPEC.md. Key deliverables:
Service Implementation (agynio/threads)
- Go gRPC service implementing
ThreadsService(8 RPCs) frombuf.build/agynio/api - Postgres data store (pgx) with 4 tables:
threads,thread_participants,messages,message_recipients - Notification publishing: on
SendMessage, callsNotificationsService.Publishwith eventmessage.created, roomthread_participant:{participantId} - Config:
DATABASE_URL,GRPC_ADDRESS,NOTIFICATIONS_ADDRESSenv vars
Reference Repos (patterns to follow)
agynio/agent-state— Postgres-backed Go gRPC service (pgx, migrations, buf codegen, Dockerfile)agynio/notifications— Go gRPC service (Makefile, Helm chart without base-chart, CI/release workflows)
CI/CD Workflows
ci.yml— PR: buf codegen, lint, test, buildrelease.yml— main push: edge image; tag push: semver image + Helm chart to GHCR
Helm Chart
charts/threads/— deployment, service, serviceaccount templates- gRPC port 50051, DATABASE_URL + NOTIFICATIONS_ADDRESS env vars
Bootstrap Integration (agynio/bootstrap_v2)
- Add
threads-db(Postgres) +threads(service) ArgoCD applications - Add corresponding variables and locals in
stacks/platform/
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels