[Extensions] When actions are delayed and run asynchronously they should be associated an identity #3850
Labels
Build Libraries & Interfaces
discuss
Issues intended to help drive brainstorming and decision making
enhancement
Enhancement or improvement to existing feature or request
extensions
Identity
PR/Issues associated with Authentication or Authorization
Priority-High
Is your feature request related to a problem? Please describe.
There are many long running / scheduled / asychronous processes within OpenSearch and plugins, When these tasks are executed they do not have the context of who triggered them. For management purposes it would be useful to know if there was a specific user/process causing instability, or to allow for restricted permissions of the tasks themselves when completed.
Describe the solution you'd like
All task execution should have an associated identity (#3846), furthermore, tasks that are executed in response to another task should be associated.
Additional context
The job-scheduler plugin embodies these scenarios, how its capabilities are integrated with OpenSearch might be a good fit for this work to happen in that codebase, or might inform if it should be incorporated into OpenSearch core.
The text was updated successfully, but these errors were encountered: