-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Set-AzureRmResource gives input object cannot be bound error #8240
Comments
@yxie97 I'm unable to reproduce this exception with other resource types. Would you mind doing the following: (1) Uninstall all instances of |
@yxie97 Ping |
Hi @maddieclayton , I am also facing same issue with Set-AzureRmResource command. Few of my scripts were working fine since last year and now since January they have started reporting error.
It fails with below error:
Can you please check and suggest what could be the issue here. |
@praharshp Can you provide the information that Cormac requested above? " (1) Uninstall all instances of |
@maddieclayton thanks for replying. Unfortunately I cannot try that. The servers where the issue is observed are customer production environments and many other scripts are running on them without any issues. Can you suggest similar steps to capture debugging logs on AzureRm that might help in your investigation. |
Same issue here. Checked on few PCs. Including a fresh installation of Windows 10 and PowerShellModules. Just a few commands (as described on Set-AzureRmResource docs: https://docs.microsoft.com/en-us/powershell/module/azurerm.resources/set-azurermresource?view=azurermps-6.13.0)
Throws:
|
@TomaszOledzki Would you be able to provide the information requested from the original poster? |
I'm super frustrated. Can't something just work?
|
And no, this is a fresh machine. There is no |
@would you be able these two items? |
Hello Everyone, i just tested this and it seems to be related to the the piping. Try this: This appears to work EDIT: Apparently it will run and complete with that flag added , but won't actually change the ip restrictions. Seems it may be related to the command then in the new version, was having issues on 6.7.0 |
Hi All As tspring418 suggested, this command works for me. I was able to update/change iprestrictions and save using following command Looks like the issue is in example on the docs site not having correct parameters for Set-AzureRmResource command. |
The fix for this issue can be found here: #8593 It looks like PowerShell was trying to convert the |
Just for the records, executing this:
won't work. No exception is thrown, but also nothing happens! |
@JohannesHoppe Yeah, i found that to be the case as well. I edited my comment previously to state that there is no change in the ip restrictions when i tested this, so it seems to run fine but doesn't actually perform anything, which is certainly strange! |
This is very frustrating! How I am supposed to manage our (expensive) infrastructure on Azure? By hand??? |
Example code I'm using to update existing rule in ipSecurityRestrictions. Works on AzureRM 6.13.1 and Api 2018-11-01:
|
The fix for this piping scenario will be available in the upcoming release of @JohannesHoppe would you mind filing a separate issue for the bug you're seeing with |
@cormacpayne I reported my issue in #8784. Unfortunately 1.5.0 had no effect to my issue. 😞 |
@JohannesHoppe thanks for filing the separate issue -- I just want to mention that 1.5.0 shouldn't have any effect on the issue you're seeing with certain properties not getting updated, since we only fixed the broken piping scenario, but we will investigate the issue you (and others) are seeing that's outlined in the issue you opened. |
@JohannesHoppe @tspring418 passing $WebAppConfig.Properties rather than $webAppConfig for -Properties fixed the issue , please find the details
|
Description
Started to have a weird issue after installing AzureRm 6.13.1. Even simplest code (get a resource and set it back) as below:
throws an excpetion:
Now even after I uninstalled 6.13.1, I am still getting this issue
Script/Steps for Reproduction
Module Version
Environment Data
$PSVersionTable
Debug Output
The text was updated successfully, but these errors were encountered: