hardcoded-response-rules.example.yml

#  Copyright 2022 Nikita Petko <petko@vmminfra.net>
#
#  Licensed under the Apache License, Version 2.0 (the "License");
#  you may not use this file except in compliance with the License.
#  You may obtain a copy of the License at
#
#      http://www.apache.org/licenses/LICENSE-2.0
#
#  Unless required by applicable law or agreed to in writing, software
#  distributed under the License is distributed on an "AS IS" BASIS,
#  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
#  See the License for the specific language governing permissions and
#  limitations under the License.

# Hardcoding responses is a bad practice, but sometimes it's necessary.

# Route template is a regex that will be matched against the request URI (without the query string).
- routeTemplate: .* # Matches any request URI. If the route template is not specified, this value will be inferred from the route.
  hostname: "*" # Matches any hostname. If the hostname is not specified, this value will be inferred.
  method: "*" # Matches any method. If the method is not specified, this value will be inferred.
  scheme: "*" # Matches any scheme. If the scheme is not specified, this value will be inferred.
  statusCode: 200 # If not specified, defaults to 200
  body: { "hello": "world" } # If not specified, defaults to empty string
  headers: # An K/V Map of headers to respond with.
    # If not specified, defaults to empty map
    # Example:
    Content-Type: application/json
    X-Api-Key: "12345"
    X-Another-Header: "67890"
    Test-Header: "Test-Value"