-certificate parameter needed on the Install-Module cmdlet
I have built an internal Powershell Gallery where all uploaded (Powershell related) items are signed but I am in an 'Allsigned' environment mandated from 'on high' that cannot be changed which means that every time someone uses the 'Install-Module' cmdlet at the moment, unless they're installing something directly from my, self-managed, internal Gallery, whatever they've decided to install and download can't work unless they go find it and sign it as a seperate step. It would present less of a barrier to adoption to people if the downloading of a module from a repository allowed them to run the downloaded .ps1, .psm1, .psd1, .ps1xml etc files affected by our AllSigned policy and sign them as they go (assuming that they have been granted or otherwise obtained a codesigning certificate already).
As described, this seems to us to be problematic to implement in the core cmdlets for security reasons.
However, there may be workarounds available. Please contact firstname.lastname@example.org if you wish to follow up.