Post-analysis of code coverage, these are the major hot spots to focus for test coverage
Longer team projects/investments that are not necessarily aligned with a specific milestone
This is a project to track:
The experience for developing PowerShell modules or using the PowerShell API
This includes anything related to:
No description
Issues that impact the ability to use PowerShell either due to conflicts with Linux/Mac norms or cmdlet coverage. This includes (but is not limited to) problems related to:
Our goal for the future of PowerShell Remoting Protocol (PSRP) is to funnel it over the SSH (Secure SHell) protocol. This will enable bi-directional PowerShell Remoting between Windows, macOS, and Linux. On Windows, this work is dependent on our Win32 port of OpenSSH. On Linux, this work will leverage the existing, ubquitious OpenSSH client/server.
This work includes integration with Enter-PSSession, New-PSSession, and Invoke-Command (more information in this RFC). Also, see this related RFC.
While PowerShell Remoting (PSRP) over OpenSSH is our plan for the future of PowerShell remoting, we also recognize the difficulty in deploying new servers (e.g. OpenSSH) to existing Windows Server deployments in the enterprise.
Therefore, for macOS/Linux -> Windows remoting scenarios, our goal is to enable existing remoting cmdlets (e.g. Enter-PSSession, New-PSSession, and Invoke-Command) using the traditional WSMan protocol. This currently works for basic authentication as well as for NTLM-based authentication from (only) Linux environments.
I can know how many people are using PowerShell (incl. version and platform) and how the community is growing.
An effort to expand the set of Linux distros on which we build, run, test, and package PowerShell.
For Beta1:
No description
No description
