EPIC Goal

Captures the work related to test infrastructure for the new feature of sending notifications on new template version

Background/Feature Origin

With software template versioning support added by RHIDP-6905, if a template gets updated, notify owners of that template (owner(s) of the app that used it) that a new version is available, using RHDH's notification mechanisms, so they know they can update if they want to stay on the latest version.

The owner of a component can be a user or a group of users.

Why is this important?

The ability to notify component owners of an update to a software template could be beneficial in that it would allow the owners to see whenever dependencies and other related requirements have changed. This can help them in understanding if there is a need to re-run or make changes to their component.

User Scenarios

• As a platform engineer (or software template owner), after I have created a new version of a template, I want RHDH to send a notification to all the components created by this template. The receiver will be the component's owner
• As an owner of a component, I could be a user or a group. The notification should be sent to the correct user or group. 
• As a platform engineer, I want to be able to configure the title and content of a message in the RHDH configuration with the following example:

Title: <catalog entity name> is out of sync with template
Message content: The template used to create <catalog entity name> has been updated to a new version. Review and update your entity to stay in sync with the template.
Button label: Edit
  * As a platform engineer, I want to make sure that RHDH can send hundreds or thousands of notifications, as this is how many components could have been created from a single template. We want to ensure that notifications are not dropped, lost.

Dependencies (internal and external)

There was some work around evaluating the events system, need to follow up on this

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>