Support namespace isolation option for Dapr PubSub

[olitomlinson]

In what area(s)?

/area runtime

Describe the feature

In the same vein as namespace isolation support for State Management building block in v1.8 (namespace option), please can dapr PubSub support namespace isolation too.

An opt-in configuration when enables any topics and queues that are created in the underlying pub/sub broker include the namespace as well as the AppID in the name, so that messages don't bleed across namespaces, even if the AppID are not the same.

Given two apps, with a need for pub sub topic :

Namespace : NS-1
AppID : Foo
Topic : Command

Namespace : NS-2
AppID : Foo
Topic : Command

would lead to the creation of two discrete queues, something like :

NS-1.Foo.Command
NS-2.Foo.Command

[yaron2]

Thanks @olitomlinson! Triaged to 1.9.

[olitomlinson]

Awesome. Thanks so much.

[olitomlinson]

@yaron2

Just an update, my development teams are starting to move forward with adopting Dapr PubSub, so its essential for us that this is resolved quickly, as our entire development cluster relies on multiple dev/test copies of the application stack being deployed and we can't allow messages to collide across those stacks.

[yaron2]

@yaron2

Just an update, my development teams are starting to move forward with adopting Dapr PubSub, so its essential for us that this is resolved quickly, as our entire development cluster relies on multiple dev/test copies of the application stack being deployed and we can't allow messages to collide across those stacks.

This is still on track for 1.9