Get-HPOVProfile -Name $var returns all profiles when $var is empty

[uzimmermann42]

Please fill in as much information as possible to help resolve your issue.

Expected Behavior

When using an option switch like -Name, it should error when no variable or string is provided

Actual Behavior

It returns all profiles

Steps to reproduce

ps> $shortname
ps> Get-HPOVProfile -Name $shortname

<List of all profiles>

Version Information

HPE OneView PowerShell Library Version (Get-HPOVVersion or $PSLibraryVersion):

HPOV                                LibraryVersion Path
----------------------------        -------------- ----
ApplianceVersion: 4.20.01.385523.01 4.20.1971.1960 C:\Users\...\Documents\WindowsPowerShell\Modules\HPOneView.420\4.20.1...

Output from $PSVersionTable on your Windows Host:

Name                           Value
----                           -----
PSVersion                      5.1.14393.2969
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.2969
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

[ChrisLynchHPE]

Ah, it appears that the -Name parameter is missing the [ValidateNotNullOrEmpty()] parameter tag. It also appears that a few other parameters in that Cmdlet are missing that parameter tag as well.

I'll get that fixed in the next 4.20 library update.

[uzimmermann42]

Yeah, it caused is a big headache as a coworker had used it with "Get-HPOVProfile -Name $shortname | Remove-HPOVProfile -Confirm:$false -force". The "-force" and the missing [ValidateNotNullOrEmpty()] caused all profiles on that instance to be now in bad states and we have to delete and redo them all. I told him not to use -force.

[ChrisLynchHPE]

-Force should only be used in rare cases where the hardware management processor (iLO) is not reachable and the profile needs to be removed.

[uzimmermann42]

That is what I told him.

On Wed, Jun 5, 2019 at 11:30 Chris Lynch ***@***.***> wrote: -Force should only be used in rare cases where the hardware management processor (iLO) is not reachable and the profile needs to be removed. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#405>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABI4PJWT6FM2S4WSAH4H4PLPZAA2NANCNFSM4HUBFSPA> .

-- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-396-1764 You can find my resume at: http://www.Alameda.net/~ulf/resume.html

[uzimmermann42]

By the way, thanks for the quick response. This was much better than at us say the HPE OneView support via Datacenter Care ... I dread calling them.

[ChrisLynchHPE]

This was fixed in Release 4.20.2133.3186 and in PowerShell Gallery.

Apologies for the extremely late response to this issue.

Please verify before this issue is closed.

[ChrisLynchHPE]

Closing due to no further activity. If you wish, feel free to re-open to discuss further.