Request for Dynamic Tenant Name Support in Apache Pulsar for Dapr

[samjabeen]

Describe the feature

I would like to propose the addition of the capability to pass tenant names dynamically when publishing events in Apache Pulsar within a multi-tenant system using Dapr.

Background:

Currently, our architecture supports a multi-tenant solution utilizing Apache Pulsar, allowing for seamless integration of new tenants without requiring additional deployments. However, managing separate pub/sub component files for each tenant can be cumbersome and inefficient, especially as the number of tenants increases.

Proposed Solution:

Implement functionality that allows applications using Dapr to dynamically specify the tenant name during the event publishing process. This would enable:

• Onboarding new tenants without needing to create separate pub/sub component files for each one.
• Reducing the overhead associated with maintaining numerous component files.
• Allowing applications to easily onboard new tenants without requiring additional deployments or deployment processes.

Use Case:

By enabling dynamic tenant name support, we can streamline our onboarding process for new tenants, allowing for more efficient management of our multi-tenant system.

Release Note

RELEASE NOTE: