Pipeline Notify not honoring delegate selection
complete
U
Uniform Harrier
Currently we do not consider the delegateSelectors while sending the notifications via delegate. This is a request for the Notification Service to honour the DelegateSelector config, if the notification is configured to be sent through Delegate.
Log In
A
Abhishek Thamman
complete
A
Abhishek Thamman
Hey @dUniform Harrier, marking this feature request as "Complete" as the support for sending notifications through Delegates was made available. Documentation: https://developer.harness.io/docs/platform/notifications/centralised-notification/
You can track https://ideas.harness.io/feature-request/p/delegate-expression-in-pipeline-notifications for the support of Delegate expressions.
This post was marked as
in progress
Prateek Mittal
Hi Douglas,
This is a fair feedback and a known gap in the system. We are currently working on a feature where you can select delegate for the notifications. We will let you know once it is available.
Thanks,
Prateek
Prateek Mittal
under review
U
Uniform Harrier
Does it actually reliability send out the webhooks messages? I'm asking because when I do use the delegateSelectors, I seem to get a different number of notifications compared to if I use your public ones. Is there a way I can tell when a webhook message is sent via that notify...do you capture outgoing messages?