microsoftgraph / microsoftgraph/entra-powershell
🙏 Get-EntraBetaAgentIdentity should support a Get based on agentIdentityBlueprintId (aka AgentAppId), in addition to -AgentId
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 213
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Describe the feature
Today this cmdlet only takes an objectId as an input. It should also support agentIdentityBlueprintId (aka AgentAppId in the cmdlets) as an alternative input.
How will this feature enhance your project and further the project’s overall goals? Who will benefit from this feature (i.e. all users; the project team)?
Simplify the experience for a user who has the agentIdentityBlueprintId handy, but not the objectId.
Describe alternatives you've considered
N/A
Additional context
N/A
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.
Research direction
Start at the Get-EntraBetaAgentIdentity cmdlet and trace how -AgentId is processed. Add agentIdentityBlueprintId, also called AgentAppId, as an alternative lookup input, then verify that either identifier returns the expected agent identity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100