Work Pool and Work Queue update events

[soamicharan]

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

[zzstoatzz]

hi @soamicharan - thanks for the issue!

this makes sense to me on face value, the only hesitation I'd have is around making sure we don't have too many events emitted by default (so maybe a setting?).

are you interested in contributing a PR for this?

[soamicharan]

@zzstoatzz if we may generalize this enhancement then we can have setting that enables to push events if specific data is created/updated/deleted from database.
For example Work_queues, wotk_pool, deployments, flows table row is updated/created /deleted we can create a event
We can generate events by using SQLAlchemy orm events?

[zzstoatzz]

@soamicharan if I'm understanding correctly, events for all CRUD operations is something we could certainly explore in a discussion, but would likely be outside the scope of this issue as written