Repository navigation
Feature Request: Pipeline Input #214
Description
This module should support pipeline input where possible.
Get-MgUser -UserId e5c3398d-6401-4dd6-bb87-6d3f95499aef | Get-MgUserLicenseDetail
Get-MgGroup -GroupId 0f764d03-afb6-45cd-a720-84708fc0d5dc | Get-MgGroupMember | Get-MgUserReacted by Matt Hamilton, Merill Fernando, Douglas Baker, Balázs Orbán and Micah Rairdon
Activity
mabster commentedon Jun 14, 2022
I'm sure the team has their own ideas on how this could work, but I feel like adding an alias property to the output of the commands would be a good solution.
For example:
... so now the output has a
GroupIdproperty that's the same asId.Now all that's necessary is to add the
ValueFromPipelineByPropertyNameattribute to theGroupIdparameter onGet-MgGroupMember.I realise this is easier said than done, given that you're auto-generating the functions.
peombwa commentedon Oct 26, 2022
We are still waiting for the code generator (AutoREST.PowerShell) to support
ValueFromPipelineByPropertyNamefor path parameters. This is being tracked in Azure/autorest.powershell#616peombwa commentedon Aug 23, 2023
A breaking change will occur because we will need to drop support for
-InputObjectparameter set to support piping byValueFromPipelineByPropertyName- Get-MgUser (Microsoft.Graph.Users) | Microsoft Learn.AutoREST uses
-InputObjectto support piping viaValueFrompipeline, which doesn't work for MS Graph as explained at Azure/autorest.powershell#616. Adding support for piping viaValueFromPipelineByPropertyNamehas the effect of breaking customers who've taken a dependency on the publicly documentedInputObjectparameter.calebkiage commentedon Feb 28, 2024
Tim (@timayabi2020), is there a design for this feature put down anywhere?