Epic Goal

• Generate an event that can notify the user on image expiration

Why is this important?

• Currently users have no way of being alerted when an image is about to expire
• Users want to be able to know when an image is about expire, so that do not run into unexpected pull failures
• Users need to be aware about both, images expiring because of individual tag expiration and also images that are soon to be captured by time-based pruning policies

Scenarios

1. An image that has expired will notify via email, Slack webhooks, and ect
2. An image that is about to expire will notify via email, Slack webhooks, and ect
3. Users can configure these events at the repository level
4. Image event triggers for Images expiring within 30/15/7/3/1 day(s)
5. Image event triggers for images that will be captured by either an org-level or repo-level image pruning policy that is time-based (currently tag age limit, in the future also last pull date)

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. Image pruner dry-run functionality?

Previous Work (Optional):

1. ...

Open questions::

1. How will we know when an image is expiring?
2. Will we need to update the database schema to account for image expiration?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• 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 Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>