Static response with no backend or fake/void backend

[Gounlaf]

Is your feature request related to a problem? Please describe. I would like to use the Static Proxy feature. I'm in the case stated in documentation:

Another example scenario is to create an endpoint pointing to an unfinished backend where its functionality is not in production yet, but your client application needs to go ahead the backend developers and start using the static responses.

The documentation is clear enough (IMO) about the behavior: the static response is merged at the end of the process.

So, I understand that a backend is always required.

Describe the solution you'd like A "void" or "fake" backend would be nice, in order to avoid errors:

• a real backend will be contacted, and probably return 4XX or 5XX if the endpoint doesn't exist
• a backend that doesn't exist will produce a tcpdialup error

Configuration used:

{
  "version": 2,
  "extra_config": {
  },
  "output_encoding": "json",
  "name": "api-gateway",
  "port": 8080,
  "endpoints": [
    {
      "endpoint": "/static/response/with/json",
      "method": "GET",
      "output_encoding": "json",
      "extra_config": {
        "github.com/devopsfaith/krakend/proxy": {
          "static": {
            "strategy": "always",
            "data": {
              "wrapped": [
                {
                  "whatever": "data"
                },
                {
                  "whatever": "other data"
                }
              ]
            }
          }
        }
      },
      "backend": []
    }
  ]
}

Response:

krakend-1  | ERROR parsing the configuration file: '/etc/krakend/krakend.json': WARNING: the 'GET /static/response/with/json' endpoint has 0 backends defined! Ignoring
krakend-1 exited with code 255

[kpacha]

the proposed behavior is hard to check. that's why an endpoint with no backends is always rejected as errored.

one solution if you don't want to generate errors is to consume the /__debug/ endpoint from the gateway and deny the message field.

[github-actions[bot]]

This issue was marked as resolved a long time ago and now has been automatically locked as there has not been any recent activity after it. You can still open a new issue and reference this link.