microsoftgraph / microsoftgraph/entra-powershell
Pipeline support in Entra PowerShell
@KenitoInc is already working on this.
Since May 13, 2024.
- Dominant language
- PowerShell
- Stars
- 213
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
It looks like Entra PowerShell is going into another extreme compared to the Microsoft.Graph that's famous for almost nonexistent pipeline support.
Let's look, for example, at the Get-EntraUser and Get-EntraGroup commands. All their parameters accept the pipeline input ByValue and ByPropertyName. There is no a single reason for that kind of design. Why would -All and -Top parameters accept the pipeline input? Just because that's wrongly executed in AzureAD module?
Things that are wrong in AzureAD (another example is a Boolean -All parameter) should not be inherited in Entra PowerShell.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.