recurring-task-creator

Recurring Task Creator

Publishes task.CreateCommand events to Kafka on a fixed schedule so a downstream task-controller materializes recurring tasks (daily / weekly / weekday / monthly / quarterly / yearly) as Obsidian vault .md files.

Task definitions live as Kubernetes Schedule Custom Resources — adding / editing / removing a recurring task is kubectl apply, not a code release.

How it works

kubectl apply -f schedule.yaml          ← operator
        │
        ▼
   K8s API server  (Schedule CRD, group task.benjamin-borbe.de/v1)
        │ watch
        ▼
   recurring-task-creator pod  ← installs the CRD at boot,
                                 runs an informer in its own pod
                                 namespace, hourly tick reads from
                                 the cache
        │ task.CreateCommand
        ▼
   Kafka  ← topic per vault (e.g. task-command-personal)
        │
        ▼
   agent-task-controller pod  ← consumes the topic,
                                writes the markdown file
        │
        ▼
   Obsidian vault git remote  ← committed by the controller

Identifiers are deterministic: UUID5("recurring-<slug>-<period-token>"), where the period token is YYYY-MM-DD (daily), YYYYWww (weekly), YYYYWww-<3-letter-weekday> (weekday), YYYY-MM (monthly), YYYYQN (quarterly), YYYY (yearly). The downstream controller dedups on identifier → safe to re-publish every tick, safe to manual /trigger?date=YYYY-MM-DD replay, safe to crash-restart.

Define a schedule

See k8s/apis/task.benjamin-borbe.de/v1/testdata/example.yaml for the canonical shape:

apiVersion: task.benjamin-borbe.de/v1
kind: Schedule
metadata:
  name: weekly-review              # frozen — UUID5 input
  namespace: default               # the recurring-task-creator pod watches its own namespace
spec:
  vault: default                   # routes to agent-task-controller-<vault>
  title: Weekly Review             # Go text/template; period token suffixed by publisher
  schedule:
    recurrence: Weekday            # Daily | Weekly | Weekday | Monthly | Quarterly | Yearly
    weekday: Saturday              # required iff recurrence == Weekday (Monday..Sunday)
  template:
    body: |
      Reflect on the past week.
      Plan the next.
    frontmatter:                   # YAML frontmatter stamped onto the generated task file
      priority: 2
      status: in_progress
      page_type: task
      assignee: bborbe

The CRD's OpenAPI schema enforces the recurrence enum, the weekday enum, and a CEL rule that requires weekday iff recurrence == "Weekday".

Build + deploy

make test                          # ginkgo specs + coverage
BRANCH=dev  make buca              # build, push image, apply STS + RBAC to dev
BRANCH=prod make buca              # same for prod

make buca is a small chain (make build && make upload && make apply). The applied tree is the binary deployment only — StatefulSet, Service, KafkaUser, Role + RoleBinding for namespace-scoped Schedule watch, and ClusterRole + ClusterRoleBinding for the CRD self-install.

Schedule CRs themselves live in a separate (typically private) repository — they reference the deployed image but are operator-owned data, not part of the binary. The repo deployer applies them with kubectl apply -k <overlay> (kustomize) or any GitOps mechanism of choice.

RBAC

The pod's ServiceAccount needs:

• apiextensions.k8s.io/customresourcedefinitions get / create / update / patch at cluster scope — for the boot-time CRD install
• task.benjamin-borbe.de/schedules get / list / watch in the pod's own namespace — for the informer

Manifests: k8s/recurring-task-creator-{sa,clusterrole,clusterrolebinding,role,rolebinding}.yaml.

Local smoke-test

DRY_RUN=true ./recurring-task-creator-run-once -logtostderr -v=2

Skips Kafka init entirely (uses a noop sender); logs every (slug, date, identifier) triple the publisher would send. Use to verify a Schedule's behavior before deploying.

Repo layout

License

BSD-2-Clause. See LICENSE.