Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NamespaceManager doesn't allow to discover namespace tier / capabilities #42

Closed
SeanFeldman opened this issue Jun 20, 2017 · 5 comments
Closed

Comments

@SeanFeldman
Copy link
Contributor

Current version of NamespaceManager does not allow to discover namespace capabilities (tier, max entity size, etc).

/cc @djrosanova

@SeanFeldman
Copy link
Contributor Author

I've seen this affecting SB360, Cerebrata Cerulean, SBExplorer - they all require users to provide information about namespace type rather than being able to read it using NamespaceManager. From a user (and a developer) point of view that's a usability issue. Would be really nice if this could be addressed.

Cerebrata Cerulean:
image

SB360:
image

@yvesgoeleven
Copy link

💯 Yes please, our tools could be a lot better if we knew what type of namespace we were dealing with

@paolosalvatori
Copy link

As the author of the Service Bus Explorer, I raised this issue many times in the internal distribution lists. Let me raise this again. It's extremely important that you add a method or a property to retrieve the namespace type as this is important to understand which entities to retrieve at runtime. The tool already provides the ability to specify which entities to retrieve (queues, topics, notification hubs, event hubs, relays), but this is left to the user, while it would be great if this could be automated. Thanks

@binzywu binzywu self-assigned this Jul 12, 2017
@SeanFeldman
Copy link
Contributor Author

Thank you for categorizing this feature request.
Would it be possible to assign a milestone to have an idea when it might be available?

@SeanFeldman
Copy link
Contributor Author

This is now possible with the new client and ManagementClient (.NET Standard client).

@axisc looks like some old issues might be no longer needed if fixes are deployed.

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

No branches or pull requests

4 participants