[feature request]: debug/dry-run endpoint

[abeforgit]

For development and debugging, it would be nice to have a way to see the "execution plan" resources would send to mu-auth, without it actually sending it

something like:

GET /dry-run
{
  query: "/my/resource?filter[foo]=bar",
  method: GET,
  headers: {} 
  //etc
}

I feel like this could be a good first issue to get familiar with the code?

[madnificent]

This would be a hard issue to tackle.

mu-cl-resources executes various queries. Some queries are constructed based on responses from earlier queries. There are algorithms in place to determine what the steps are but there is no abstract strategy defined in data.

It would be a good introduction to check what mu-cl-resources executes to find the necessary data, but it would be a hard first issue to build a dry-run endpoint with the current code-base.