Use a queue to manage events #2
Description
Currently, the Azure function rules are directly called from the Azure DevOps service hook. The downside to that is that if there is any issue (Azure function downtime, bug...) the event is lost and it's not possible to retry it.
Also, as soon as the function has a few issues, the service hook is put in restricted mode on the Azure DevOps side meaning it's not called anymore.
In order to manage that issue, the idea would be to use a message queue in between the aggregator functions and Azure DevOps.
That would provide a retry functionality and improve the global resilience of the solution.