Azure / Azure/azure-powershell
Was the -Namespace parameter changed to -NamespaceName in Az.ServiceBus? I can't find a migration guide.
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 4.3k
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 54
Description
### 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
```PowerShell
##[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
```PowerShell
```
### Module versions
```PowerShell
Az.ServiceBus 4.0.0
```
### Error output
```PowerShell
Parameter cannot be processed because the parameter name 'Namespace' is ambiguous. Possible matches include: -NamespaceName -NamespaceInputObject.
```
Contributor guide
Research direction
Start with the Az.ServiceBus 4.0.0 parameter definitions for Get-AzServiceBusQueue, Get-AzServiceBusTopic, and the other commands using Namespace. Determine whether Namespace was replaced, identify every affected command, and document the migration guidance and corrected parameter names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- cli, cloud
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100