feat(temporal): run maintenance directly in Temporal - #2005
Draft
shepherdjerred wants to merge 2 commits into
Draft
feat(temporal): run maintenance directly in Temporal#2005shepherdjerred wants to merge 2 commits into
shepherdjerred wants to merge 2 commits into
Conversation
Owner
Author
|
This change is part of the following stack: Change managed by git-spice. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Run Kometa and Buildkite maintenance entirely inside Temporal activities. The four existing schedule IDs and workflow names are preserved, but they now target a dedicated
maintenancequeue handled by one serial worker.What changed
Bun.spawnactivities with Temporal heartbeats, cancellation termination, secret redaction, retry propagation, and success/failure metrics.temporal-maintenance-workerDeployment inbuildkite, pinned toliskov, with Recreate strategy and one concurrent activity.Verification
git diff --check: passed.127.0.0.1:7233and fail when that server is unavailable.Post-deploy acceptance
After ArgoCD sync, run each workflow once and verify the maintenance pod is Ready, Kometa updates Plex, cache/Trivy storage behavior is correct, metrics and stale-run alerting are present, and no maintenance Kubernetes Jobs are created.