Start a Conversation

Unsolved

This post is more than 5 years old

957

July 12th, 2016 12:00

Please make Compellent PowerShell cmdlets Case Insensitive.

Dear Compellent PowerShell team;

Please make the parameters for the Powershell cmdlets case insensitive. Here's an example to show why I'm asking:

     $FluidFSParams = @{connection=$Global:DellConnection;ClusterID=$Global:ClusterId;NasVolumeId=$VolID}
     $QuotaUsageObject = Get-DellFluidFsUserQuotaUsage @FluidFSParams -UserName $User

In this case, if I happen to get the case of the user wrong, the usage object is not found. If I use the following method:

     $QuotaUsageObject = Get-DellFluidFsUserQuotaUsage @FluidFSParams | where-Object{$_.UserName -eq $User}

I would have to process upwards of 30,000 objects to find the quota object I'm interested in. Also, though not a technical argument per se, this is a Windows emulation using the Windows .NET infrastructure which is inherently case insensitive. I was quite surprised when the case of the input data mattered.

Please and (I hope) Thank you.

No Responses!
No Events found!

Top