Skip to content

fix(configurator): retire failed S3 runners and enable production email - #284

Merged
lweberru merged 1 commit into
mainfrom
fix/retire-reported-s3-apply-runners
Nov 20, 2026
Merged

lweberru merged 1 commit into
mainfrom
fix/retire-reported-s3-apply-runners

Conversation

@lweberru

Copy link
Copy Markdown
Collaborator

Two production gaps prevented normal use after v2.2.1: reported failed S3 workers could remain desired STARTED, keeping checkpoint inspection blocked, and production email had never been provisioned/bound.

Background maintenance now retires only source-verified runners of explicitly reported S3 apply_failed runs after a completion grace period. It verifies stopped tasks/processes before recording a scheduling timestamp; checkpoint and confirmation still recheck actual CF status. State, run recovery hold, locks and migrations remain intact. Timeouts, ambiguous failures, bootstrap/pending migration and separate recovery State stay excluded. Migration 101 adds only scheduling metadata/functions and an index.

Add a separate reviewed Prod MailOut manifest, stage-isolated private bindings, asynchronous domain handling and strict DNS conflict protection. The production workflow requires the protected SMTP binding, passes it only to the application runtime and verifies the actual binding before SMTP checks. Existing branded templates and per-user topic preferences apply. The provider domain, DNS records and sender are active; uploading credentials to the protected GitHub environment is pending explicit approval required by automatic review. Credentials are never printed or committed.

Validation: full application check (2,180 tests passing, 100 skips including the separately executed database group); all 86 isolated PostgreSQL Plan/Apply cases; 19 CF stopped-runner tests; operator MailOut/production tests; workflow catalogue checks; bilingual operator/recovery documentation. Release notes for v2.2.2 are curated. No customer State was modified or run reconciled. Assistant knowledge/model behavior is unchanged; existing qualification limitations remain documented.

@lweberru
lweberru merged commit 56f0d69 into main Nov 20, 2026
16 checks passed
@lweberru
lweberru deleted the fix/retire-reported-s3-apply-runners branch November 20, 2026 17:09
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.

1 participant