Overview:

Introduce a "Last Pulled" column in the Tags view of a repository within Quay. This feature provides users with the date and time a tag was last pulled, eliminating the need to manually extract this information from audit logs. By making this data readily accessible, tag management becomes more efficient and intuitive.

Business Requirements:

• Display the "Last Pulled" timestamp directly in the Tags view for each repository.
• Ensure the information is updated dynamically based on pull activity.
• Provide users with easy visibility into tag usage patterns, supporting better lifecycle and storage management decisions.

Customer Benefit:

• Improved Tag Management: Enables users to identify inactive or unused tags for pruning, saving storage and reducing clutter.
• Enhanced Usability: Simplifies workflows by removing the need to search audit logs for pull information.
• Operational Efficiency: Supports automated and manual workflows for repository maintenance.

Scope:

1. Add a "Last Pulled" column in the Tags view of the Quay UI.
2. Display the most recent pull timestamp for each tag.
3. Update the UI dynamically to reflect the latest pull activity.
4. Provide API support to expose "Last Pulled" data programmatically.

Acceptance Criteria:

UI Updates:

• • The "Last Pulled" column is visible in the Tags view for all repositories.
  • Accurate timestamps are displayed for each tag, reflecting the last pull time.

API Support:

• • An API endpoint provides "Last Pulled" data for tags.
  • The data aligns with what is displayed in the UI.

Performance:

• • The "Last Pulled" column does not impact UI performance or loading times.

Data Availability:

• • If a tag has never been pulled, the column should display "Never Pulled" or a similar placeholder.

Out of Scope (for Initial Release):

• Advanced analytics or reporting based on "Last Pulled" data.
• Historical trends or detailed logs of pull activity per tag.