feat: add contextual_handler() decorator
Contextual event handler functions receive a primary value as an argument, with additional context value provided to implicitly using a `ContextVar`. This separation allows a handler function to act primarily on an important subset of incoming event data, but still access the wider event metadata when needed, and automatically include metadata in `ExecutionInfo` result values (using the `contextual_default_factory()` pattern). Incoming events are separated into the primary value and context value by a parser function that receives the incoming event value from the parent handler. The `@contextual_handler(...)` decorator is the interface to this functionality.
-
mentioned in merge request uis/devops/gsuite/management-functions!38
-
mentioned in merge request uis/devops/iam/activate-account/account-data-manager!2 (merged)
-
mentioned in merge request uis/devops/iam/activate-account/entra-event-handler!26
-
mentioned in merge request uis/devops/devhub/lookup-gitlab-sync/faas!35
-
mentioned in merge request uis/devops/iam/ibis/institution-mapping-tool!13
-
mentioned in merge request uis/devops/infra/terraform/ucam-faas-long!82 (merged)
-
mentioned in merge request uis/devops/infra/terraform/ucam-faas!130 (merged)
-
mentioned in merge request uis/devops/gsuite/management-functions!49
-
mentioned in merge request uis/devops/devhub/lookup-gitlab-sync/faas!57
-
mentioned in merge request uis/devops/iam/activate-account/account-data-manager!64
-
mentioned in merge request uis/devops/iam/activate-account/entra-event-handler!47