Fire Arrow 2.2.0

Fire Arrow 2.2.0 has been released.

• (feature) Post-request pre-response hooks are now supported
• (enhancement) Telemetry sent to Azure Application Insights now contains full request graph
• (enhancement) Per-request caching speeds up multiple retrieval of dependencies

Fire Arrow now supports two request hooks:

• Post-validation, pre-request: This hook can be used to inject custom, business-case specific validation logic (added in 2.1.0)
• Post-request, pre-response: This hook can be used to modify the respose before it is sent to the client. Example use cases include on-the-fly anonymization or data enrichment (added in 2.2.0)

This release also greatly enhances telemetry sent to Azure Application Insights. Fire Arrow now supports the Open Telemetry traceparent header and will properly group its own requests in the parent's span ID. This allows visibility into performance bottlenecks, especially when validation requires complex sub-requests before a response can be generated.

Fire Arrow now also speeds up nested resource retrieval. If lists of Observations were retrieved and for each Observation the Patient entity needed to be retrieved, Fire Arrow needed to handle each Patient entity through a single request (as each request is subject to re-validation). These requests are now cached, so that multiple retrievals of the same entity can be returned directly from memory.