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

Unused exports in Service Bus package since version 1.1.3 #7991

Closed
ramya-rao-a opened this issue Mar 24, 2020 · 5 comments
Closed

Unused exports in Service Bus package since version 1.1.3 #7991

ramya-rao-a opened this issue Mar 24, 2020 · 5 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Service Bus
Milestone

Comments

@ramya-rao-a
Copy link
Contributor

The @azure/service-bus package has interfaces being exported that are not in use. These correspond to the management api features that have been implemented internally, but are not ready for public use yet.

#7315 took care of ensuring these features are not accidentally exported, but it missed cleaning out a few interfaces.

8329a7c cleans up the above in the master branch, but the same needs to be cherry-picked as a hot fix to v1 as well

The current state is misleading users that these features are indeed public. See https://stackoverflow.com/questions/60759318/how-to-obtain-queuedetails-from-a-servicebus-queue

cc @chradek, @HarshaNalluru

@ramya-rao-a ramya-rao-a added Client This issue points to a problem in the data-plane of the library. Service Bus labels Mar 24, 2020
@ramya-rao-a ramya-rao-a added this to the [2020] April milestone Mar 24, 2020
@chradek
Copy link
Contributor

chradek commented Mar 24, 2020

Related to #7938

@simonauner
Copy link

Thanks for picking this up. I was actually trying to create the SO question with the tag azure-sdk-js mentioned in the README, but since no questions have been asked with that tag previously I couldn't add it (too low rep to create new tags).
And yes, it looks like @tchelidze in #7938 is trying to achieve the same thing.

@ramya-rao-a
Copy link
Contributor Author

Closing this issue as we have now released version 1.1.5 with the unused exports mentioned above removed from the public api surface as well as the documentation. The lone sample that used the management features is removed as well until we have the feature ready for public use

Please subscribe to #1057 to get notified when the ATOM management client makes it to the public api surface.

Until then, please use @azure/arm-servicebus for all the management needs.
If you cannot use AAD and have to use connection string for these features, then use the older azure-sb package until @azure/service-bus has similar features.

@ramya-rao-a
Copy link
Contributor Author

ramya-rao-a commented Jun 10, 2020

Hello!

We are happy to share that the third preview to v7 (7.0.0-preview.3) of the @azure/service-bus package now supports the CRUD & list operations on queues, topics, subscriptions and rules via a separate "client" that can be instantiated either via a connection string or an AAD credential.

Please checkout the sample for management operations for more details.

Please note that this is still in preview and the next preview might have some changes in the API based on internal and external feedback.

Please give it a try and let us know if you have any feedback.

@simonauner
Copy link

Works like a charm, exactly what I wanted. Thanks a lot!

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Service Bus
Projects
None yet
Development

No branches or pull requests

4 participants