Summary
The export-seed CI workflow currently polls /api/v1/data/stats as a readiness check to detect when the app is ready after ingestion. With the addition of Spring Boot Actuator in #33, there is now a proper health endpoint at /actuator/health that serves the same purpose.
/api/v1/data/stats remains permitAll() solely because the CI workflow depends on it being unauthenticated. It is not called from the frontend UI.
Proposed changes
- Update
export-seed.yml — change the readiness poll from /api/v1/data/stats to /actuator/health
- Move
/api/v1/data/stats behind auth — remove it from permitAll() in SecurityConfig.kt
Why this is safe
IngestionRunner is an ApplicationRunner, so the app only accepts HTTP requests after ingestion completes. /actuator/health has the same readiness semantics as /api/v1/data/stats — both return only after the full application context is up.
IngestionRunner calls dataManager.getStats() directly (in-process method call), so it is unaffected by this change.
Summary
The export-seed CI workflow currently polls
/api/v1/data/statsas a readiness check to detect when the app is ready after ingestion. With the addition of Spring Boot Actuator in #33, there is now a proper health endpoint at/actuator/healththat serves the same purpose./api/v1/data/statsremainspermitAll()solely because the CI workflow depends on it being unauthenticated. It is not called from the frontend UI.Proposed changes
export-seed.yml— change the readiness poll from/api/v1/data/statsto/actuator/health/api/v1/data/statsbehind auth — remove it frompermitAll()inSecurityConfig.ktWhy this is safe
IngestionRunneris anApplicationRunner, so the app only accepts HTTP requests after ingestion completes./actuator/healthhas the same readiness semantics as/api/v1/data/stats— both return only after the full application context is up.IngestionRunnercallsdataManager.getStats()directly (in-process method call), so it is unaffected by this change.