Skip to content

fix: stop the schedule seed overwriting operator edits - #2951

Merged
sparrowDom merged 1 commit into
masterfrom
fix/seed-insert-only
Jul 28, 2026
Merged

fix: stop the schedule seed overwriting operator edits#2951
sparrowDom merged 1 commit into
masterfrom
fix/seed-insert-only

Conversation

@sparrowDom

@sparrowDom sparrowDom commented Jul 27, 2026

Copy link
Copy Markdown
Member
  • Remove the issue where any deploy of the runner would overwrite the prod db user edited commands
  • don't apply the seed.sql twice. The runner already does it.

Should be deployed along: https://github.com/oplabs/talos/pull/23

#2848 changed the seed's conflict clause to DO UPDATE SET command so the
46 existing rows would migrate from `pnpm hardhat <task>` to the new
`pnpm exec tsx tasks/run.ts <task>` invocation. Seeds re-run on every
runner boot, so that also silently overwrote parameters operators had set
in the admin UI: on 2026-07-27 the deploy reset all 46 rows to stock
defaults, losing the flags on stake_validator and remove_validator.

The migration it was added for has now completed — the seed applied on
the 23:15:59Z boot, so every row already carries the tsx invocation.
Reverting to DO NOTHING therefore loses nothing and stops future deploys
from clobbering operator state. cron_expr, enabled and signer_override
were never in the clause and were unaffected throughout.

Also drop the duplicate seed application in runner.ts: runContainer
already applies every migrations/seed_*.sql before starting the
scheduler, so this ran the same file twice per boot and bypassed the
client-side seed validation.
@sparrowDom
sparrowDom merged commit 8b86cd7 into master Jul 28, 2026
11 checks passed
@sparrowDom
sparrowDom deleted the fix/seed-insert-only branch July 28, 2026 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants