Skip to content

[FEATURE REQ] [Microsoft.Azure.WebJobs.Extensions.EventHubs] Custom Endpoint support feature falls short when using AMQP and more than one event hub per Azure Function App #45672

Open

Description

Library name

Microsoft.Azure.WebJobs.Extensions.EventHubs

Please describe the feature.

The current implementation of Custom Endpoint allows its value to be set only once in the host.json file.

This limitation becomes problematic when attempting to connect to multiple Event Hub Namespaces from a single Azure Function App.

For example, if using an application gateway in front of your Event Hubs, you’ll need to add a listener for each Event Hub Namespace you want to support via AMQPS. Consequently, if you have an Azure Function with a trigger from one namespace and a binding to another, there is no way to configure it correctly.

We should be able to set the custom endpoint in the triggers and bindings, or in a map inside the host.json file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    ClientThis issue points to a problem in the data-plane of the library.Functionscustomer-reportedIssues that are reported by GitHub users external to the Azure organization.feature-requestThis issue requires a new behavior in the product in order be resolved.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions