{"action":"opened","issue":{"url":"https://api.github.com/repos/Particular/NServiceBus.Transport.AzureServiceBus/issues/20","repository_url":"https://api.github.com/repos/Particular/NServiceBus.Transport.AzureServiceBus","labels_url":"https://api.github.com/repos/Particular/NServiceBus.Transport.AzureServiceBus/issues/20/labels{/name}","comments_url":"https://api.github.com/repos/Particular/NServiceBus.Transport.AzureServiceBus/issues/20/comments","events_url":"https://api.github.com/repos/Particular/NServiceBus.Transport.AzureServiceBus/issues/20/events","html_url":"https://github.com/Particular/NServiceBus.Transport.AzureServiceBus/issues/20","id":376100182,"node_id":"MDU6SXNzdWUzNzYxMDAxODI=","number":20,"title":"Support namespace hierarchy","user":{"login":"markgould","id":2712328,"node_id":"MDQ6VXNlcjI3MTIzMjg=","avatar_url":"https://avatars2.githubusercontent.com/u/2712328?v=4","gravatar_id":"","url":"https://api.github.com/users/markgould","html_url":"https://github.com/markgould","followers_url":"https://api.github.com/users/markgould/followers","following_url":"https://api.github.com/users/markgould/following{/other_user}","gists_url":"https://api.github.com/users/markgould/gists{/gist_id}","starred_url":"https://api.github.com/users/markgould/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/markgould/subscriptions","organizations_url":"https://api.github.com/users/markgould/orgs","repos_url":"https://api.github.com/users/markgould/repos","events_url":"https://api.github.com/users/markgould/events{/privacy}","received_events_url":"https://api.github.com/users/markgould/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-31T18:21:39Z","updated_at":"2018-10-31T18:21:39Z","closed_at":null,"author_association":"NONE","body":"I would like to request that the namespace hierarchy feature from the full framework transport is added to this one. See: https://docs.particular.net/transports/azure-service-bus/namespace-hierarchy\r\n\r\nI would like to use one Service Bus namespace for multiple dev/test environments, rather than paying for several namespaces.\r\n\r\nThe workaround right now is to customize the endpoint name to have a prefix/suffix with something that uniquely identifies the environment. Forward slashes are not supported, as currently the topic subscriptions are named with the queue names. \r\n\r\nHaving to change the endpoint name is not ideal as now this effects how the tables are named when using SqlPersistence (and I assume other persistence libraries). We routinely copy databases from Prod into Dev/Test and now these tables are going to be named different per environment.\r\n\r\nIt doesn't have to be as powerful as the one in the full ASB transport. Something that looks like below would work nicely:\r\n\r\n```\r\nendpointConfiguration.UseTransport<AzureServiceBusTransport>().PathGenerator(name => \"dev1/\")\r\n```\r\n\r\nUsing the above code, if the endpoint is named \"Sender\", it would then create a queue called \"dev1/Sender\", a topic called \"dev1/bundle-1\" and then in SqlPersistence the tables would continue to be named Sender_OutboxData, Sender_SomeSaga\"\r\n\r\n"}}
{"actor":{"display_login":"markgould"}}