Nick SzaunigandClaude Sonnet 5 e7b157ec35 feat: sync calendar entries to a Microsoft 365 group calendar ...

Adds a one-way push (ApiCore -> M365) of Aufgaben/Durchsichten/
Behandlungen/Fütterungen/Ernten/Königinnen-Zuordnungen into the calendar
of a Microsoft 365 group, via the Graph API.

- CalendarSyncModule (app-only client-credentials Graph auth, separate
  from the interactive SSO app registration; new env vars
  M365_CALENDAR_TENANT_ID/_CLIENT_ID/_CLIENT_SECRET).
- Outbox + minute-interval cron worker (CalendarSyncOutboxEntry) instead
  of a synchronous push, since Graph calls are too slow/flaky to block a
  domain create request on; failed syncs retry up to 5 times.
- Per-source-type toggle plus a group-ID field, configurable in
  Verwaltung > Automatisierung > Kalender-Sync (Verwaltung > Backup, an
  env var still wins on those fields where one applies to related config).
- Hooked into Tasks/Inspections/Treatments/Feedings/Harvests/Queens at
  their existing create (and Task update/complete) points; entries render
  as all-day Graph events to avoid timezone ambiguity.
- Documents the design decision in ARCHITECTURE.md (Annahme 9), since
  this is a net-new capability the lastenheft doesn't scope.

Co-Authored-By: Claude Sonnet 5 <[email protected]>

2026-09-04 09:23:35 +02:00

..

configmap.example.yaml

feat: expand backup to all data and add automatic scheduled backups

2026-09-03 11:33:48 +02:00

deployment.yaml

feat: Backend migriert die Datenbank beim Start selbst statt ueber Job

2026-08-26 22:33:44 +02:00

ingress.yaml

fix: address code-review findings (startup validation, shutdown hooks, health check, deploy config)

2026-08-25 23:07:29 +02:00

secret.example.yaml

feat: sync calendar entries to a Microsoft 365 group calendar

2026-09-04 09:23:35 +02:00

service.yaml

feat: Grundgeruest fertigstellen (Backend/Frontend/K8s)

2026-08-21 05:17:26 +02:00