You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched the issue queue to verify this is not a duplicate feature request.
I've pasted the output of kargo version, if applicable.
I've pasted logs, if applicable.
Proposed Feature
Notification integration - e.g. for a high-profile change, we should be able to post to a Slack channel; a blocked pipeline should result in a Jira ticket; etc.
Motivation
For Slack integration, his would be an important step if there were manual promotions/approvals required.
For Jira, it would be nice to automatically open a ticket with whatever error message caused a blocked pipeline.
The text was updated successfully, but these errors were encountered:
Adding to this the requirement that we actually build a general-purpose / vendor-neutral notification system that supports pluggable integrations -- some of which may be developed by the community or other third parties.
I don't expect v0.9.0 to introduce any built-in notifications, but #2219 should leave a viable framework in place for developing such integrations as first, or more-likely, third-party steps.
Checklist
kargo version
, if applicable.Proposed Feature
Notification integration - e.g. for a high-profile change, we should be able to post to a Slack channel; a blocked pipeline should result in a Jira ticket; etc.
Motivation
For Slack integration, his would be an important step if there were manual promotions/approvals required.
For Jira, it would be nice to automatically open a ticket with whatever error message caused a blocked pipeline.
The text was updated successfully, but these errors were encountered: