routing
Explain Policy
Changed onCompile a policy and return the plan, without dispatching anything.
Operator-gated, and deliberately so: the response enumerates the policy's targets, which is exactly the information a policy exists to keep off the wire. It is a management surface, not a caller-facing one.
Accepts an unsaved spec as well as a saved name, so a form can validate what the operator is about to save. The response includes dropped candidates with reasons, which is the part that catches a "failover" policy that has quietly compiled down to a single attempt.
post/api/v1/routing/policies/explain
Request
- The document declares no server URL.
- Auth: one of:
- API key in header Otari-Key
- API key in header x-api-key
Request body
Response
Successful Response
Changes
- info
added the optional property
to the response with the status
- info
- info
api operation id
explain_policy_api_v1_routing_policies_explain_postremoved and replaced withrouting-explain_policy
- info