Make notification method configurable
in progress
Y
Yarrow Crane
User wanted to make notification method configurable so this will significantly improve usability. because at this moment, when configuring pipeline notifications, the notification method is not configurable, which is very rigid and forces all development team to stick to the same notification mechanism.
Log In
Rohan Gupta
Merged in a post:
How to setup Alert Notification Rules as described
A
Amber Duck
How to setup "Alert Notification Rules" as described below?
1) Any "Approval" Notification only be sent to the approval groups of the workflow or pipeline.
We have different groups which own different workflows/pipelines, we don't want to be notified with those alerts, instead, only the corresponding group can be notified.
2) Only show "group sync failure" on Harness UI, do not send notification to any group.
Currently, we setup a rule to filter the alert type "group sync failure" by setting "not match" + alert type "group sync failure", but we still keep receiving the notifications.
Rohan Gupta
Merged in a post:
Feature Request : Need an ability to send teams notifications on adhoc basis (Notification pre built template)
L
Lavender Pony
Feature Request : Need an ability to send teams notifications on adhoc basis (Notification pre built template)
At this moment Harness provides out of box Email template only in a custom stages, Here in VSX we are looking for an ability to send custom TEAM's notification as part of pipeline execution. It would be nice if you Harness can provide an out of box notification step in which we have an ability to
Choose notification type email or teams or slack (VSX needs Team's integration)
Provide an ability to choose the channel to which notification needs to be sent.
Ability to configure notification step in CI & CD stages as well.
As of now VSX team is using curl approach to send notification which works but that adds additional job maintenance and coding efforts to send teams notification, If Harness can provide this capability out of the box it would be nice.
R
Raspberry Platypus
Just adding that CapGroup requested this as well. Seems it's in progress though
Maximillian Printz
This could be as simple as allowing the notification method in pipeline notifications to be either a runtime input or an expression.
Context was to be able to use vars to send emails, using a pipeline var, so when making a pipeline template they don't have to hard code the same email every pipeline that uses the template, but to have the email be an input the developer can set when using the template.
Rohan Gupta
in progress