-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Get-AzureRmServiceBusTopic does not return more than 100 topics #6891
Comments
@v-Ajnava Can you take a look at this issue? |
@wagsousa, if the namespace is standard, you can create 100 topics with EnablePartitioning $True, by default - without -MaxCount parameter, get cmdlets will give you 100 resources. please try the get cmdlets with -Maxcount with latest AzureRm release and let me know if still face the issue. |
I tested with 103 topics and MaxCount to 200 and I don't see the issue but we can create up to 10k topics/queues with EnablePartitioning $False. |
@wagsousa will add the message in the cmdlet help and update the thread. |
Closing as fixed. |
I can't access topics more than 1000, I'm trying to iterate through all topics and make an update, this seems impossible with powershell, is that true? |
@AceHack, can you please help us the command you are using to get the topics and also the namespace you are using here. |
Description
Get-AzureRmServiceBusTopic is ignoring nextLink parameter consequently does not return more than 100 topics.
please also check queue cmdlet (Get-AzureRmServiceBusQueue)
Script
Create more than 100 topics on the Service Bus namespace and run Get-AzureRmServiceBusTopic
New-AzureRmServiceBusTopic -ResourceGroup RGNAME -NamespaceName NAMESPACENAME -TopicName topic1 -EnablePartitioning $True
Module Version
Debug Output
The text was updated successfully, but these errors were encountered: