Closed khushboobhatia01 closed 3 years ago
Why is this change necessary? --> We have notification configured as part of workflows and action. And an action can be executed directly or by a workflow. This leads to notifications getting triggered multiple times.
What is the downside if this change is not implemented? -> Our rules engine and notifier pods have been running at 100% utilisation because of number of executions across fleet (workflow). Disabling action triggers when ran under workflow context will help us reduce load.
Are there any potential security implications for changing this? -> I don't think so.
https://docs.stackstorm.com/chatops/notifications.html#how-do-i-setup-notifications-for-orquesta Specifying notify parameter as [] doesn't work. https://github.com/StackStorm/st2/blob/master/st2common/st2common/services/workflows.py#L789 I guess this is where it filters the tasks and set notify parameter of live action. However, this is overridden when we request action at https://github.com/StackStorm/st2/blob/master/st2common/st2common/services/workflows.py#L802 by https://github.com/StackStorm/st2/blob/master/st2common/st2common/services/action.py#L134. There seems to be some bug.
Can you write a better description for this?