Persist opted-in payment processor data with PostgreSQL #38
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
asmo/cashu-operator!38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/persistent-processor-data"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A stateful gRPC payment processor can need durable local data even when the mint ledger uses PostgreSQL. Currently that combination mounts emptyDir, so replacing the pod discards the processor's local state.
Add the opt-in CashuMint annotation
mint.cashu.asmogo.github.io/persist-processor-data: "true". With an enabled processor sidecar, reconcile and mount the existing data PVC, select Recreate, and reject more than one replica. Existing behavior remains unchanged without the annotation; no CRD changes are required.Include regression tests and generic migration guidance. This does not copy existing data or convert database formats: installations must preserve and restore existing processor state before activating the annotation. Recreate prevents overlap during normal rollouts, not force deletion or independently started wallet instances.
Validation:
go test ./internal/controller/generators ./internal/controller -count=1passed with Kubernetes 1.34.1 envtest assets, including the full local API-server suite.git diff --checkpassed.Prepared against current main (v0.4.2 baseline). This PR does not publish a release or deploy anything; it can be included in a subsequent v0.4.3 release after review.