unkin/argocd-apps
3
0
Fork 0
Code Issues 7 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

pdbmux: order backends new-first and drop primary/prefer #452

Merged
benvin merged 1 commits from benvin/pdbmux-backend-order into main 2026-09-05 16:04:40 +10:00
Conversation 0 Commits 1 Files Changed 2
+6 -10
unkin-agent commented 2026-09-05 12:05:54 +10:00
Member
Copy Link
Copy Source

Why

pdbmux#9 drops primary/prefer and makes configured backend order the only tie-break, so the current old-first list would silently reverse which PuppetDB wins.

How

  • Order PDBMUX_BACKENDS with new=http://puppetdb.puppet.svc.cluster.local:8080 first and old=http://puppetdbapi.service.consul:8080 second, URLs unchanged.
  • Drop PDBMUX_PRIMARY and PDBMUX_PREFER; both already resolve to new, on the deployed v0.1.0 image (estate defaults) and on pdbmux main (first-backend fallback), so the rendered behaviour is unchanged today.
  • Refresh the configmap and deployment comments to describe order-based precedence.

Merge this before pdbmux#9.

## Why pdbmux#9 drops primary/prefer and makes configured backend order the only tie-break, so the current `old`-first list would silently reverse which PuppetDB wins. ## How - Order `PDBMUX_BACKENDS` with `new=http://puppetdb.puppet.svc.cluster.local:8080` first and `old=http://puppetdbapi.service.consul:8080` second, URLs unchanged. - Drop `PDBMUX_PRIMARY` and `PDBMUX_PREFER`; both already resolve to `new`, on the deployed v0.1.0 image (estate defaults) and on pdbmux main (first-backend fallback), so the rendered behaviour is unchanged today. - Refresh the configmap and deployment comments to describe order-based precedence. Merge this before pdbmux#9.
unkin-agent added 1 commit 2026-09-05 12:05:54 +10:00
pdbmux: order backends new-first and drop primary/prefer
ci/woodpecker/pr/vector-test Pipeline was successful
Details
ci/woodpecker/pr/pre-commit Pipeline was successful
Details
ci/woodpecker/pr/kubeconform Pipeline was successful
Details
079978e883 
Prepare for pdbmux#9, which removes the primary/prefer concept and makes
configured backend order the only tie-break. Listing new first keeps the
k8s PuppetDB the winner; primary/prefer already resolve to new today, so
the rendered behaviour is unchanged until #9 lands.
benvin merged commit 1172aa3e96 into main 2026-09-05 16:04:40 +10:00
benvin deleted branch benvin/pdbmux-backend-order 2026-09-05 16:04:41 +10:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
benvin (BenVincent) unkin-agent (Unkin Agent) unkinben (Ben Vincent)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/argocd-apps#452
Delete Branch "benvin/pdbmux-backend-order"

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?