In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

We do a few JSON.parse() that we should replace with https://github.com/fastify/secure-json-parse. It's not strictly a security issue, but it would be great to do it to protect against possible attacks.

Enterprise Gateway documentation spans various roles and forms for information. It would be helpful to have this reorganized based on a consumer's role. Something similar to how the Jupyter Server or Zero to JupyterHub docs would be nice.

Sections for