Find-PSResource Functionality

[SydneyhSmith]

In the initial proposal for PowerShellGet 3.0 we combined all Find-* cmdlets into a single command--Find-PSResource--which allows users to discover Scripts, Modules, DSCResources, Commands, and RoleCapabilities using a -Type parameter filter.

After more discussion, there are two main types of PSResources, those that can be installed vs those that are subcomponents of modules which cannot be installed directly (they must be installed as a part of a module package).

Should we break up Find-PSResource into two separate commands?

• Find-PSResource for modules and scripts
• Find-Command for commands

As a lower priority

• Find-DSCResource for DSCResources