Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Cmdlets to Get and Remove EngineEvents #21513

Open
kilasuit opened this issue Apr 22, 2024 · 1 comment
Open

Add Cmdlets to Get and Remove EngineEvents #21513

kilasuit opened this issue Apr 22, 2024 · 1 comment
Labels
Issue-Enhancement the issue is more of a feature request than a bug Needs-Triage The issue is new and needs to be triaged by a work group. WG-Cmdlets general cmdlet issues

Comments

@kilasuit
Copy link
Collaborator

Summary of the new feature / enhancement

As a user I want an easy way to Register, then Get, and the Remove engine events using builtin cmdlets

Proposed technical implementation details (optional)

Add the following Cmdlets
Get-EngineEvent
Remove-EngineEvent

@kilasuit kilasuit added Issue-Enhancement the issue is more of a feature request than a bug WG-Cmdlets general cmdlet issues Needs-Triage The issue is new and needs to be triaged by a work group. labels Apr 22, 2024
@jborean93
Copy link
Collaborator

What benefit do you see this having over Get-Event, Remove-Event, Get-EventSubscriber? While there is a dedicated Register-EngineEvent I believe you are meant to use the generic *-Event cmdlets to manage events that are subscribed from various providers. You can even publicly extend your own event source like I've done in PSEtw.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Enhancement the issue is more of a feature request than a bug Needs-Triage The issue is new and needs to be triaged by a work group. WG-Cmdlets general cmdlet issues
Projects
None yet
Development

No branches or pull requests

2 participants