tegwick
b3b0c3e3ff
Some checks failed
railiance-tests / smoke (push) Has been cancelled
- Add RAIL-BS-WP-0008 (activity-core WP-0016 deploy) and RAIL-BS-WP-0009 (admin-sync smoke) from inbox asks 87952ff1 / aa8b7986 - Archive finished workplans to workplans/archived/ per ADR-001 convention; normalize frontmatter statuses (completed/done -> finished) - Fill stack-and-commands.md, complete repo-boundary.md, refresh SCOPE Current State, add docs/operator-runbook.md for production-touching targets Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
47 lines
1.5 KiB
Markdown
47 lines
1.5 KiB
Markdown
---
|
||
id: RAIL-BS-WP-0009
|
||
type: workplan
|
||
title: "activity-core no-restart admin-sync smoke (ACTIVITY-WP-0012-T05)"
|
||
domain: financials
|
||
repo: railiance-cluster
|
||
status: ready
|
||
owner: railiance-cluster
|
||
topic_slug: railiance
|
||
created: "2026-07-01"
|
||
updated: "2026-07-01"
|
||
---
|
||
|
||
# activity-core no-restart admin-sync smoke (ACTIVITY-WP-0012-T05)
|
||
|
||
## Context
|
||
|
||
Inbox message `aa8b7986` (activity-core, 2026-06-18): activity-core commit
|
||
`3e93567` implements ACTIVITY-WP-0012 T01–T04 (shared sync_service,
|
||
`POST /admin/sync`, explicit schedule upsert/pause/orphan-delete counts,
|
||
worker startup reuse, runbook docs; 192 tests passed). T05 is the
|
||
cluster-owned smoke: prove admin sync works **without** worker
|
||
SIGTERM/pod restart.
|
||
|
||
The deploy precondition is covered by RAIL-BS-WP-0008-T01 (main at
|
||
`bf877b7` ≥ `3e93567`), so run this after that reconcile.
|
||
|
||
## Run the no-restart admin-sync smoke
|
||
|
||
```task
|
||
id: RAIL-BS-WP-0009-T01
|
||
status: wait
|
||
priority: medium
|
||
```
|
||
|
||
After RAIL-BS-WP-0008-T01 is deployed, without restarting the worker:
|
||
|
||
1. Change or use a customer ActivityDefinition enabled-flip/rename fixture.
|
||
2. Call `POST /admin/sync?definitions=true&schedules=true` from the operator
|
||
path.
|
||
3. Confirm the new Temporal schedule is active and the retired/disabled
|
||
schedule is paused or deleted per sync semantics.
|
||
4. Confirm event-triggered definitions still fire normally.
|
||
5. Record non-secret evidence in the State Hub. Response JSON should include
|
||
`definitions.synced`, `schedules.upserted`, `schedules.paused`,
|
||
`schedules.deleted_orphans`, and `errors[]`.
|