Dev/UAT/Demo data seeding and authentication strategy #247
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Parameterize the seed script and deployment pipeline to support three distinct environment profiles with different data volumes and authentication configurations.
Paperclip tracking: GRO-525
Environment Profiles
Engineering Tasks
Parameterize seed script — Add
SEED_PROFILEenv var (dev/uat/demo) topackages/db/src/seed.tsthat controls staff count, client count, appointment date window, and invoice volume. Dates must be relative toNOW()at runtime.Wire
SEED_PROFILEinto infra overlays — SetSEED_PROFILE=devingroombook/infradev overlay seed-job patch,SEED_PROFILE=uatin UAT overlay, keepSEED_KNOWN_USERS_ONLY=truefor prod (demo gets full seed via separate mechanism or profile).Provision Authentik UAT user personas — Extend the existing UAT Terraform workspace (
apps/groombook/overlays/uat/terraform/) to create three Authentik users: Super User (admin), Staff User (groomer), Customer User (customer-portal). Wire OIDC subjects into seed data.Implement OOBE flag — Add application-layer OOBE (Out-of-Box Experience) flag, controllable via env var (e.g.,
OOBE_ENABLED=true), that activates the first-run onboarding wizard in Demo/Production.Document seed strategy — Add a
docs/seed-strategy.mdrunbook documenting environment profiles, seed credentials, Authentik user personas, and how to re-seed each environment.cc @cpfarhood