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

Was the -Namespace parameter changed to -NamespaceName in Az.ServiceBus? I can't find a migration guide. #27013

Open
sanfordn opened this issue Jan 16, 2025 · 3 comments
Labels
customer-reported needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus

Comments

@sanfordn
Copy link

Description

In Az.ServiceBus, we have a lot of scripts that use -Namespace as the parameter to them.

(Get-AzServiceBusQueue -ResourceGroupName $resourceGroup -Namespace $namespace,
Get-AzServiceBusTopic -ResourceGroupName $resourceGroup -Namespace $namespace,
etc.)

I noticed a release from 2 days ago. Was there a breaking change made to modules that use -Namespace instead of -NamespaceName? Which commands does this impact? I'm seeing signs that it might not just be the servicebus commands.

Script or Debug output

##[error]Parameter cannot be processed because the parameter name 'Namespace' is ambiguous. Possible matches include: -NamespaceName -NamespaceInputObject.

##[debug]System.Management.Automation.ParameterBindingException: Parameter cannot be processed because the parameter name 'Namespace' is ambiguous. Possible matches include: -NamespaceName -NamespaceInputObject

Environment data

Module versions

Az.ServiceBus 4.0.0

Error output

Parameter cannot be processed because the parameter name 'Namespace' is ambiguous. Possible matches include: -NamespaceName -NamespaceInputObject.
@sanfordn sanfordn added needs-triage This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 16, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported needs-triage This is a new issue that needs to be triaged to the appropriate team. and removed needs-triage This is a new issue that needs to be triaged to the appropriate team. labels Jan 16, 2025
@isra-fel
Copy link
Member

@YanaXu could you help check it? Thanks

@microsoft-github-policy-service microsoft-github-policy-service bot removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jan 23, 2025
@YanaXu
Copy link
Contributor

YanaXu commented Jan 24, 2025

Hi @sanfordn,

This breaking change is introduced by Az.ServiceBus 2.0.0, which is released on 10/17/2022.
The latest Az.ServiceBus version is 4.1.0.
Did you recently upgrade Az.ServiceBus from a very old version to the latest one?

PS C:\> docker run -it  mcr.microsoft.com/powershell
PowerShell 7.4.2
PS /> Install-Module -Name Az.ServiceBus -RequiredVersion 1.11.0 -Repository PSGallery -Force
PS /> Import-Module Az.ServiceBus
PS /> Get-Module Az.ServiceBus

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     1.11.0                Az.ServiceBus                       {Add-AzServiceBusIPRule, Add-AzServiceBusVirtualNetworkRule, Approve-AzServiceBusPrivateEndpointConnection, Complete-AzServiceBusMigration…}

PS /> (Get-Command Get-AzServiceBusQueue).Parameters.Keys | where {$_ -like "*Namespace*"}
Namespace
PS /> exit
PS C:\> docker run -it  mcr.microsoft.com/powershell
PowerShell 7.4.2
PS /> Install-Module -Name Az.ServiceBus -RequiredVersion 2.0.0 -Repository PSGallery -Force
PS /> Import-Module Az.ServiceBus
PS /> Get-Module Az.ServiceBus

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     2.0.0                 Az.ServiceBus                       {Add-AzServiceBusIPRule, Add-AzServiceBusVirtualNetworkRule, Get-AzServiceBusNamespace, Get-AzServiceBusOperation…}

PS /> (Get-Command Get-AzServiceBusQueue).Parameters.Keys | where {$_ -like "*Namespace*"}
NamespaceName
PS />

@isra-fel isra-fel added the needs-author-feedback More information is needed from author to address the issue. label Jan 27, 2025
@sanfordn
Copy link
Author

We must have upgraded some of our packages recently. Could you assist me in finding a migration guide to figure out which commands have been updated to be -NamespaceName instead of -Namespace so we can figure out which of our scripts need to be updated?

@microsoft-github-policy-service microsoft-github-policy-service bot added needs-team-attention This issue needs attention from Azure service team or SDK team and removed needs-author-feedback More information is needed from author to address the issue. labels Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus
Projects
None yet
Development

No branches or pull requests

4 participants