Multiple dispatching rules

[juaninicolai]

Hello, does someone know if it's possible to configure multiple dispatching rules for one mocked endpoint?

I am using JSON_BODY rule to infer which response (out of 2 options) to return.
After reading this proxy article I thought of implementing this for the same endpoint.

The implementation would be as follows (this is working fine):

{
  "exp": "/destinationLocation/rkstCode",
  "operator": "equals",
  "cases": {
    "DKAAR": "dkaar",
    "NLROT": "nlrot",
    "default": "Destination not found"
  }
}

But when trying to add the PROXY_FALLBACK configuration via UI and saving it, in the details page, the JSON_BODY rule is gone and replaced by the latter.

The configured proxy rules is this one (not working):

{
  "dispatcher": "JSON_BODY",
  "dispatcherRules": {
    "exp": "/destinationLocation/rkstCode",
    "operator": "equals",
    "cases": {
      "DKAAR": "dkaar",
      "NLROT": "nlrot",
      "default": "Destination not found"
    }
  },
  "proxyUrl": URL_HERE
}

And when hitting the endpoint I get this error from the server: Given JSON string cannot be interpreted as valid ProxyFallbackSpecification which makes me wonder if the issue is related to multiple rules or just JSON_BODY not being allowed to be wrapped by PROXY_FALLBACK.

[lbroudoux]

Have you tried converting the dispatcherRules as a String? (putting the content within "" and escaping stuffs?
I admit I never tried this but dispatcherRules being defined as String, it should work...
It may be more convenient in the future to extend the type to String | Node.
Let us know.

[juaninicolai]

Hi Laurent,

Yes, I tried passing the dispatcherRule as a String and got this error from the server: io.github.microcks.util.dispatcher.JsonMappingException: Given JSON string cannot be interpreted as valid ProxyFallbackSpecificatio at io.github.microcks.util.dispatcher.ProxyFallbackSpecification.buildFromJsonString(ProxyFallbackSpecification.java:68) so it's not working at the moment.

I will continue trying other approaches and let you know.

[juaninicolai]

Hey @lbroudoux, this version worked half-way through:

{
  "dispatcher": "JSON_BODY",
  "dispatcherRules": "{\n    \"exp\": \"/destinationLocation/rkstCode\",\n    \"operator\": \"equals\",\n    \"cases\": {\n      \"DKAAR\": \"dkaar\",\n      \"NLROT\": \"nlrot\",\n      \"default\": \"Destination not found\"\n    }\n  }",
  "proxyUrl": "URL_HERE"
}

I am gonna keep working on this and keep you posted :)
Thanks

[lbroudoux]

Are you still getting an exception here? Or does it fail somewhere else?

[juaninicolai]

Hey, no exception at the moment but I am getting a BAD_REQUEST from the mocked API, which is unexpected.
I sent a request with a non-handled value in the JSON_BODY rule, which I thought would trigger the 'default' response OR the proxy to redirect to the production API but that did not happen.

I am still working on this, will update this thread when this is working or new questions arise :)

[juaninicolai]

Now it works. It seems the 'default' rule of JSON_BODY gets disabled or does not apply when wrapped via proxy.
There was nothing wrong with the proxy dispatcher, just a wrong implementation from my side (but I learned a lot).
The above JSON rule (with strings and escaped fields) works OK.