We want to have some content source functions call another function via the Fusion HTTP API.
That requires a change to Fusion in order to expose the current deployment version in the content source (or by passing it in via a query parameter)
Guest
Thanks for this submission; however, we suggest that any logic that should be shared between content sources should either be abstracted into a separate, shared utility, or include both HTTP calls inside the same content source. The reason this is preferred is so we can use a single caching layer at one content source, rather that trying to sync caching between multiple chained content sources.