Skip to content

docs(routes): retry-policy parser landed; fix circuit-breaker scope notes#12

Open
raffaelschneider wants to merge 2 commits into
mainfrom
docs/route-retry-policy-parser-landed
Open

docs(routes): retry-policy parser landed; fix circuit-breaker scope notes#12
raffaelschneider wants to merge 2 commits into
mainfrom
docs/route-retry-policy-parser-landed

Conversation

@raffaelschneider

Copy link
Copy Markdown
Contributor

Summary

Updates the route-level retry-policy and circuit-breaker admonitions in configuration/routes.md to match reality after zentinel#267 merged (which closed #262):

  • Retry policy — no longer "dropped by the parser." The block is now parsed; max-attempts is honored (bounds upstream peer-selection attempts), while timeout-ms / backoff-base-ms / backoff-max-ms / retryable-status-codes parse but aren't applied yet. Points to the behavior follow-up zentinel#279.
  • Circuit breaker — route scope is still not parsed; reworded to direct users to the upstream-level block, now supported via zentinel#260 (merged). Removes the stale "#262 / in flight #260" wording.

Docs-only; no example KDL changed.

…pe notes

The route-level retry-policy block is now parsed (zentinel#267): max-attempts
is honored, the backoff/timeout/retryable-status-codes settings parse but are
not yet applied (tracked in zentinel#279). Route-level circuit-breaker is still
not parsed; upstream-level circuit-breaker is now supported (zentinel#260).
Replaces the stale "dropped by the parser / tracked in #262" notes.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 16, 2026

Copy link
Copy Markdown

Deploying zentinelproxy-io-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: 537bf14
Status: ✅  Deploy successful!
Preview URL: https://b2ee2dae.zentinelproxy-io-docs.pages.dev
Branch Preview URL: https://docs-route-retry-policy-pars.zentinelproxy-io-docs.pages.dev

View logs

… #260)

#260 was closed without merging; the upstream circuit-breaker config
actually shipped via #267. Also note the known open-state recovery bug (#261).
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