Work Pool and Work Queue update events #16658
Description
Describe the current behavior
The current behavior of work pool and work queue updates are if work pool/work queue status is updated then only creates a Event record in database. If Work Pool/Work Queue any other fields are updated then there is no event is created in database.
Describe the proposed behavior
Whenever work pool/work queue fields are updated then it should create a event in database so we can create some automations around work pool/work queue updates.
Example Use
One of example use case is that whenever work pool concurrency limit is updated OR work queue priority changes then we can write automations to handle subsequent actions to either notify on slack or scale resources accordingly.
Additional context
No response