You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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.
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.
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
The text was updated successfully, but these errors were encountered: