Compare commits
1 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| c26b40e299 |
@@ -19,27 +19,6 @@ GroomBook API is a Hono-based REST service (TypeScript/Node.js) powering the pet
|
|||||||
- OIDC authentication provider configured
|
- OIDC authentication provider configured
|
||||||
- Seed data present (clients, pets, services, staff)
|
- Seed data present (clients, pets, services, staff)
|
||||||
|
|
||||||
### Source of truth for UAT passwords (GRO-2000)
|
|
||||||
|
|
||||||
The `UAT_SUPER_PASSWORD` / `UAT_GROOMER_PASSWORD` / `UAT_TESTER_PASSWORD` / `UAT_CUSTOMER_PASSWORD` env vars the test orchestrator uses **must** be pulled from the live `seed-uat-passwords` Secret in the UAT cluster — never from a captured shell value, a previous run's `.env`, or a copy of the SealedSecret committed before the latest rotation.
|
|
||||||
|
|
||||||
**Canonical recipe** (works from any host with `kubectl` + cluster credentials):
|
|
||||||
|
|
||||||
```bash
|
|
||||||
SUPER=$(kubectl get secret seed-uat-passwords -n groombook-uat \
|
|
||||||
-o jsonpath='{.data.super-password}' | base64 -d)
|
|
||||||
GROOMER=$(kubectl get secret seed-uat-passwords -n groombook-uat \
|
|
||||||
-o jsonpath='{.data.groomer-password}' | base64 -d)
|
|
||||||
TESTER=$(kubectl get secret seed-uat-passwords -n groombook-uat \
|
|
||||||
-o jsonpath='{.data.tester-password}' | base64 -d)
|
|
||||||
CUSTOMER=$(kubectl get secret seed-uat-passwords -n groombook-uat \
|
|
||||||
-o jsonpath='{.data.customer-password}' | base64 -d)
|
|
||||||
```
|
|
||||||
|
|
||||||
**Why:** the Bitnami SealedSecret `apps/overlays/uat/ss-seed-uat-passwords.yaml` (in `groombook/infra`) is the single source of truth. The UAT `reset-demo-data` CronJob re-hashes these values into the `account` table on every run (idempotent — GRO-1977). A captured env var from a previous generation will not match the current hash, producing 401 `INVALID_EMAIL_OR_PASSWORD`. If the live login still 401s after pulling from the SealedSecret, the seed Job is stale — trigger `kubectl create job --from=cronjob/reset-demo-data -n groombook-uat manual-seed-$$` and retry.
|
|
||||||
|
|
||||||
**How to apply:** at the start of every UAT run that touches TC-API-1.4 / 1.5 / 1.6 / 1.7 / 3.18 / 3.21 / 3.23, refresh these four env vars from the cluster before issuing the sign-in request.
|
|
||||||
|
|
||||||
## Test Cases
|
## Test Cases
|
||||||
|
|
||||||
### 4.0 Health Check
|
### 4.0 Health Check
|
||||||
|
|||||||
@@ -1,5 +1,5 @@
|
|||||||
-- Migration: 0037_add_extra_large_to_pet_size_category.sql
|
-- Migration: 0037_add_extra_large_to_pet_size_category.sql
|
||||||
-- GRO-1979: Adds the 'extra_large' value to the pet_size_category enum.
|
-- GRO-1999: Adds the 'extra_large' value to the pet_size_category enum.
|
||||||
--
|
--
|
||||||
-- 0031_buffer_rules.sql created pet_size_category with values
|
-- 0031_buffer_rules.sql created pet_size_category with values
|
||||||
-- ('small', 'medium', 'large', 'xlarge'), but seed.ts and the drizzle
|
-- ('small', 'medium', 'large', 'xlarge'), but seed.ts and the drizzle
|
||||||
|
|||||||
@@ -1,4 +0,0 @@
|
|||||||
-- GRO-1999: 0037 was skipped on existing DBs due to a below-high-water-mark
|
|
||||||
-- journal timestamp. Re-register extra_large with a monotonic timestamp so
|
|
||||||
-- the existing UAT/persistent DBs apply it. Idempotent.
|
|
||||||
ALTER TYPE "pet_size_category" ADD VALUE IF NOT EXISTS 'extra_large';
|
|
||||||
@@ -260,13 +260,6 @@
|
|||||||
"when": 1751500000000,
|
"when": 1751500000000,
|
||||||
"tag": "0037_add_extra_large_to_pet_size_category",
|
"tag": "0037_add_extra_large_to_pet_size_category",
|
||||||
"breakpoints": true
|
"breakpoints": true
|
||||||
},
|
|
||||||
{
|
|
||||||
"idx": 38,
|
|
||||||
"version": "7",
|
|
||||||
"when": 1780000000000,
|
|
||||||
"tag": "0038_register_extra_large_pet_size_category",
|
|
||||||
"breakpoints": true
|
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
Reference in New Issue
Block a user