From e480b03d583494451e52552a43b5b2bcceed49f0 Mon Sep 17 00:00:00 2001 From: Yaron Schneider Date: Thu, 9 Sep 2021 15:00:12 -0700 Subject: [PATCH] add custom route (#1772) --- .../building-blocks/bindings/howto-triggers.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md b/daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md index 6dde81ec2..c0afc13a8 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md +++ b/daprdocs/content/en/developing-applications/building-blocks/bindings/howto-triggers.md @@ -91,6 +91,20 @@ In order to tell Dapr that the event wasn't processed correctly in your applicat res.status(500).send() ``` +### Specifying a custom route + +By default, incoming events will be sent to an HTTP endpoint that corresponds to the name of the input binding. +You can override this by setting the following metadata property: + +```yaml +name: mybinding +spec: + type: binding.rabbitmq + metadata: + - name: route + value: /onevent +``` + ### Event delivery Guarantees Event delivery guarantees are controlled by the binding implementation. Depending on the binding implementation, the event delivery can be exactly once or at least once.