EPIC Goal

When an ArgoCD job is finished, it should send a notification to the owner (it can be a user or a group) of the component to let them know that the job has succeeded or finished with an error.

The Notification mechanism is already available in Backstage/RHDH. The plugins need to call the SDK to send a message.

Background/Feature Origin

Why is this important?

When a customer is using RHDH, they should receive notifications from the ArgoCD plugin. A developer will look at other pages in RHDH and not stay on the CI or CD page. When something happens, the plugin will send a notification and the user will receive a message instantly.

User Scenarios

• As a component owner, I want to be notified when the ArgoCD job has successfully completed, with a link that redirects to the pipeline run.
• As a component owner, I want to be notified when the ArgoCD job has terminated with an error, with the error in the message and a link that redirects to the pipeline run.

Success notification
Title: Deployment Complete: ArgoCD job succeeded for [Component Name].
Text: Your pipeline run is finished.
CTA: View Run Details

Error notification
Title: Deployment Failed: ArgoCD job terminated with an error for [Component Name].
Text: [Brief description of the error].
CTA: Investigate Pipeline Run

Dependencies (internal and external)

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>