Proxy cmdlet parameter maps don't match current available parameters in v3 module
sdwheeler opened this issue · comments
Summary of the new feature / enhancement
For example, the proxy cmdlet for Update-Script removes the Force parameter from $PSBoundParameters before calling Update-PSResource. However, Update-PSResource has a Force parameter, so it should not be remove.
Proposed technical implementation details (optional)
Make sure the parameter maps are accurate for all proxy cmdlets.