File Search Chat Completions Fixture

Single-upstream fixture configuration for recording the private Chat Completions function representation of a Responses file_search tool

Category: Test fixture
Task: Single-upstream fixture configuration for recording the private Chat Completions function representation of a Responses file_search tool

Prerequisites: The matching test or replay fixture; this is not a standalone deployment configuration.

This configuration comes from the selected release. The example has not been run here; external services are not bundled.

Download the source file.

Companion resources from the same snapshot:

# Responses File Search Translation Fixture
# Requires `--features openai-responses` because these filters are opt-in.
#
# Single-upstream fixture configuration for recording the private Chat
# Completions function representation of a Responses file_search tool. The
# complete model-search-model lifecycle is demonstrated by
# file-search-chat-completions.yaml; this variant intentionally omits the
# vector-store callout because inference replay owns exactly one upstream.

listeners:
  - name: responses-file-search-chat-fixture
    address: "127.0.0.1:8080"
    filter_chains: [responses-file-search-chat-fixture]

filter_chains:
  - name: responses-file-search-chat-fixture
    filters:
      - filter: openai_responses_format
        on_invalid: reject
        headers:
          format: x-praxis-ai-format
          model: x-praxis-ai-model
          stream: x-praxis-ai-stream

      - filter: openai_responses_validate

      - filter: responses_to_chat_completions
        max_rewritten_body_bytes: 67108864

      - filter: path_rewrite
        replace:
          pattern: "^/v1/responses/?$"
          replacement: "/v1/chat/completions"
        conditions:
          - when:
              path_prefix: "/v1/responses"
              methods: [POST]

      - filter: router
        routes:
          - path: "/v1/chat/completions"
            cluster: "chat-completions-backend"

      - filter: load_balancer
        clusters:
          - name: "chat-completions-backend"
            endpoints:
              - "127.0.0.1:3001"

insecure_options:
  allow_private_endpoints: true # fixture proxies to a local controlled backend