-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Add verbose message to Get-Service when certain properties cannot be returned #24272
Copy link
Copy link
Closed
Closed
Copy link
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Cmdlets-Managementcmdlets in the Microsoft.PowerShell.Management modulecmdlets in the Microsoft.PowerShell.Management moduleWG-ReviewedA Working Group has reviewed this and made a recommendationA Working Group has reviewed this and made a recommendation
Description
Metadata
Metadata
Assignees
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugUp-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsWG-Cmdlets-Managementcmdlets in the Microsoft.PowerShell.Management modulecmdlets in the Microsoft.PowerShell.Management moduleWG-ReviewedA Working Group has reviewed this and made a recommendationA Working Group has reviewed this and made a recommendation
Type
Projects
Status
Reviewed
Summary of the new feature / enhancement
Following on from discussions in #10371 #24245 I noted that we don't make use of the verbose stream at all within
Get-ServiceIf/when #24245 is merged it would make sense to emit a verbose message when specific properties of a service cannot be returned and it reference a new example for
Get-Servicethat shows where this may be the case with more informationProposed technical implementation details (optional)
No response