FAQ | This is a LIVE service | Changelog

Add HTTP return/synchronous handler functionality

Description

Add a new decorator type which allows for functions to return more comprehensive information to the original HTTP caller.

Further details

To support synchronous request/response type events from webhooks or similar our primary intention is to have webhook notifiers make calls to an intermediary service which accepts the webhook call and puts the message data into a PubSub queue to be handled by the real function.

In some cases, the event sender (i.e. the upstream notifier) may need to actually be informed about the result of processing the event. To support these cases we should add a distinct separate message handler that allows the implementer to send suitable responses to the HTTP caller via their response.

This should build on the additions made in #31 (closed), using the execution info to build a HTTP response to send back to the original caller.

This should be separated into a module called synchronous (For refinement: naming here?).

As part of this task, the intermediary webhook handler (which should already exist) should be reworked to use this decorator internally.

Task list

Acceptance criteria

  • Synchronous (request/response) event support available in ucam-faas

Links/references

Edited by Mike Knee