work-club-manager

4 Commits

Include renames

Author	SHA1	Message	Date
WorkClub Automation	821459966c	feat: restrict admin access to club operations and rollout test environment CI Pipeline / Backend Build & Test (pull_request) Successful in 53s Details CI Pipeline / Frontend Lint, Test & Build (pull_request) Failing after 16s Details CI Pipeline / Infrastructure Validation (pull_request) Successful in 3s Details	2026-03-18 09:08:45 +01:00
WorkClub Automation	eaa163afa4	fix(k8s): stabilize keycloak rollout and align CD deploy manifests Update Keycloak probe/realm import behavior and authority config so auth services start reliably on the dev cluster, while keeping CD deployment steps aligned with the actual Kubernetes overlay behavior.	2026-03-13 06:25:07 +01:00
WorkClub AutomationandSisyphus	65e80ee334	fix(backend): move RLS initialization before app_admin role assignment Reorganize SeedDataService to establish RLS policies before granting app_admin role to prevent permission issues. Remove --no-restore flag from Dockerfile.dev to ensure proper build. Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>	2026-03-05 19:22:29 +01:00
Sisyphus CI	b7854e9571	feat(seed): add development seed data script - Create SeedDataService in Infrastructure/Seed with idempotent seeding - Seed 2 clubs: Sunrise Tennis Club, Valley Cycling Club - Seed 7 member records (5 unique Keycloak test users) - Seed 8 work items covering all status states - Seed 5 shifts with date variety (past, today, future) - Seed shift signups for realistic partial capacity - Register SeedDataService in Program.cs with development-only guard - Use deterministic GUID generation from club names - Ensure all tenant IDs match for RLS compliance - Track in learnings.md and evidence files for Task 22 QA	2026-03-03 14:23:50 +01:00