HttpRequest Automate

HttpRequest Automate streamlines Docker registry management by automatically listing images, retrieving tags, and removing outdated tags on a scheduled basis. This workflow ensures your registry remains clean and efficient, retaining only the most relevant images while sending notifications for actions taken.

7/8/2025
16 nodes
Complex
schedulecomplexschedule triggeremailsendsplitoutfiltersshautomationadvancedapiintegrationcronemailnotification
Categories:
Schedule TriggeredComplex Workflow
Integrations:
Schedule TriggerEmailSendSplitOutFilterSsh

Target Audience

This workflow is ideal for:
- DevOps Engineers: Who need to manage Docker images efficiently and keep the registry clean.
- System Administrators: Responsible for maintaining Docker registries and ensuring optimal storage usage.
- Cloud Engineers: Looking to automate Docker image management as part of their CI/CD pipelines.
- Development Teams: Who regularly push images to Docker registries and want to manage old tags automatically.

Problem Solved

This workflow addresses the challenge of managing Docker images in a registry by automating the removal of old, unused tags. It ensures that only the latest and most relevant images are retained, thus optimizing storage and maintaining a clean environment. Additionally, it provides notifications via email about removed images, ensuring transparency and awareness among team members.

Workflow Steps

  • Scheduled Trigger: The workflow initiates at 1 AM daily.
    2. List Images: It retrieves the list of images from the Docker registry.
    3. Extract Image Names: The workflow extracts the names of the images for further processing.
    4. Retrieve Image Tags: For each image, it retrieves the associated tags.
    5. Split Tags: The tags are split out for individual processing.
    6. Filter Valid Tags: Only valid and non-empty tags are retained for further action.
    7. Fetch Manifest Digest: The workflow fetches the manifest digest for each valid tag to gather additional metadata.
    8. Update Fields: Relevant fields such as name, tag, created, and digest are updated for each image.
    9. Sort by Creation Date: Tags are sorted based on their creation date in descending order.
    10. Group Tags by Image: Tags are grouped by their respective images for easier management.
    11. Identify Tags to Remove: The workflow identifies which tags should be removed, keeping only the latest and the 10 most recent tags.
    12. Remove Old Tags: The identified old tags are deleted from the registry.
    13. Send Notification Email: A notification email is sent for each removed tag, informing the team of the action taken.
    14. Execute Garbage Collection: Finally, a garbage collection command is executed to free up space in the registry.

    • Customization Guide

    Users can customize this workflow by:
    - Changing the Schedule: Modify the scheduled trigger settings to run at different times or intervals.
    - Updating Registry URL: Replace <> with the actual Docker registry URL.
    - Email Configuration: Change the toEmail and fromEmail fields in the email nodes to match the desired recipients.
    - Adjusting Tag Retention Policy: Modify the logic in the Identify Tags to Remove node to keep more or fewer tags based on specific needs.
    - Adding Additional Notifications: Incorporate more email notifications or logging mechanisms to track workflow execution and results.