New-AzureResourceLock fails to validate -LockLevel parameter

[pcgeek86]

Environment

• Windows 8.1
• PowerShell 5.0 April 2015 Preview (5.0.10105.0)
• Azure PowerShell 0.9.1

Problem

When I call the New-AzureResourceLock command, and specify a -LockLevel parameter value of ReadOnly, I receive an error.

New-AzureResourceLock : Cannot bind parameter 'LockLevel'. Cannot convert value "ReadOnly" to type "Microsoft.Azure.Commands.ResourceManager.Cmdlets.Entities.Locks.LockLevel". Error: "Unable to match the identifier name ReadOnly to a valid enumerator
name. Specify one of the following enumerator names and try again:
CanNotDelete"

The [Microsoft.Azure.Management.Resources.Models.LockLevel] .NET Enumeration clearly shows that there are three valid values:

• ReadOnly
• CanNotDelete
• NotSpecified

Expected Result

The New-AzureResourceLock command's -LockLevel parameter should accept any of the values from the [LockLevel] .NET Enumeration.

---

Why isn't this validating against the enum values properly?

Cheers,
Trevor Sullivan
Microsoft MVP: PowerShell
http://trevorsullivan.net
http://twitter.com/pcgeek86

[ravbhatnagar]

We have fixed the .Net enumeration to list only CannotDelete which is what is currently supported in PS. Supporting other lock levels has been added to the backlog.

[ravbhatnagar]

Add all the lock levels that are supported by API. Portal has already added ReadOnly. PS and CLI should support the same.

[ravbhatnagar]

Fixed.

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @rthorn17