https://praxis.fast/praxis/dev/examples/configs/pipeline/Recent content in Pipeline on PraxisHugoenhttps://praxis.fast/praxis/dev/examples/configs/pipeline/branch-chains.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/branch-chains.yaml/Filters write structured results to FilterResultSethttps://praxis.fast/praxis/dev/examples/configs/pipeline/composed-chains.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/composed-chains.yaml/Multiple named chains are composed per listenerhttps://praxis.fast/praxis/dev/examples/configs/pipeline/conditional-filters.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/conditional-filters.yaml/Filters support conditions (request phase) and response_conditions (response phase) to gate executionhttps://praxis.fast/praxis/dev/examples/configs/pipeline/failure-mode.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/failure-mode.yaml/Demonstrates open and closed failure handling for filtershttps://praxis.fast/praxis/dev/examples/configs/pipeline/grpc-condition.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/grpc-condition.yaml/The grpc condition predicate gates a filter on whether the request carries gRPC, classified from the content-type header alone (application/grpc, application/grpc+proto, application/grpc+json, or any other application/grpc+)https://praxis.fast/praxis/dev/examples/configs/pipeline/header-presence-condition.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/header-presence-condition.yaml/The headers_present condition predicate gates a filter on whether headers are present, whatever their valueshttps://praxis.fast/praxis/dev/examples/configs/pipeline/inherited-conditions.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/inherited-conditions.yaml/A named filter chain declares one conditions: block that every filter in the chain inheritshttps://praxis.fast/praxis/dev/examples/configs/pipeline/iterative-request-router-circuit-breaker.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/iterative-request-router-circuit-breaker.yaml/Demonstrates circuit breaker integration with the iterative request routerhttps://praxis.fast/praxis/dev/examples/configs/pipeline/iterative-request-router-sequence.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/iterative-request-router-sequence.yaml/Demonstrates sequential sub-request execution where each step completes before the next beginshttps://praxis.fast/praxis/dev/examples/configs/pipeline/route-on-promoted-header.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/route-on-promoted-header.yaml/Classify a request in an early filter, promote the result to a reserved x-praxis- header, and route on that headerhttps://praxis.fast/praxis/dev/examples/configs/pipeline/selected-upstream-conditions.yaml/Mon, 01 Jan 0001 00:00:00 +0000https://praxis.fast/praxis/dev/examples/configs/pipeline/selected-upstream-conditions.yaml/Gate a filter on the application metadata the load balancer publishes when it selects an upstream