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

Cannot Pipe Get-AzureRmServiceBusNameSpace to remove or other cmdlets #4340

Closed
markcowl opened this issue Jul 19, 2017 · 2 comments
Closed
Assignees
Labels
Service Attention This issue is responsible by Azure service team. Service Bus

Comments

@markcowl
Copy link
Member

Cmdlet(s)

PowerShell Version

5.1

Module Version

4.2.1

OS Version

Windows 10

Description

When attempting to pipe the output of Get-AzureRmServiceBusNamespace to Remove-AzureRmServiceBusNamespace, powershell returns an error like the following

Remove-AzureRmServiceBusNamespace : The input object cannot be bound to any parameters for the command either becaus
the command does not take pipeline input or the input and its properties do not match any of the parameters that tak
pipeline input.

Debug Output

Instructions: to get Debug Output, set $DebugPreference="Continue" and then execute the cmdlet or script causing the issue

Script/Steps for Reproduction

Get-AzureRmServiceBusNamespace | Remove-AzureRmServiceBusNamespace

@cormacpayne
Copy link
Member

@v-Ajnava Hey Ajit, would you mind verifying that this isn't an issue anymore? It seems like it should be fixed, but if not, this should be as easy as adding an -InputObject parameter to the Remove-AzureRmServiceBusNamespace cmdlet that has the ValueFromPipeline property

@v-Ajnava
Copy link
Member

fixed in the latest release

@bsiegel bsiegel added the Service Attention This issue is responsible by Azure service team. label Sep 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Service Attention This issue is responsible by Azure service team. Service Bus
Projects
None yet
Development

No branches or pull requests

5 participants