Skip to content
Explore the preview
Browse workflow ideas

Make room in a shared image library without losing a version you still need.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

Review stored image versions, keep the latest 10 tags for each image with the latest tag always preserved, and list older candidates for cleanup. Give an administrator the proposed removals and retention context to verify against deployment and recovery needs before any deletion or storage cleanup takes place.

Explore the simulation Explore the idea

Actual availability depends on published steps, supported connections, permissions, and provider approval.

Illustrative workflow and outcome
Stored image versions for reviewImage names, version tags, and relevant retention information from an organization’s shared image library
“Identify versions outside the agreed retention window, preserve the latest 10 tags and latest tag, and hold deletion and cleanup for administrator approval.”
Work through the request.

Clear tasks, with review where it matters.

  1. Confirm the image library and owner
  2. Review version tags and retention
  3. Prepare candidates for removal
See all 5 tasks
A proposed cleanup list with retained versions, candidates for removal, and status information for an administrator.

What this workflow could do

Helps operations teams review accumulated image versions and plan storage cleanup with a clear retention record.

Review points proposed in this idea

An old-looking version may still support a deployment, rollback, investigation, or recovery. Confirm the latest 10 tags and latest tag are retained, check dependencies and backups, and require an authorized administrator to approve each destructive change and any maintenance activity before it runs.

How the idea could work

Select an illustrative task to explore its proposed role. No workflow runs here.

Explore the sequenceStep 1 of 5

  1. Verify the intended environment, its administrator, and the purpose of the proposed cleanup.

Step 1 of 5

Confirm the image library and owner

Verify the intended environment, its administrator, and the purpose of the proposed cleanup.

Proposed setup considerations

These are planning notes for the concept, not instructions for a currently available template.

  1. 01

    Choose the environment and image owner

    Select the shared image library, identify its administrator, and confirm who may request cleanup.

  2. 02

    Set the retention policy

    Define how many tags to preserve for each image; the example keeps 10 and always retains the latest tag.

  3. 03

    Define approval, backup, and maintenance practices

    Specify how administrators check dependencies, recovery copies, maintenance timing, and every proposed deletion.

  4. 04

    Test with a non-production example

    Review retained and removable tags, cancellation, and failure notifications without deleting production material.

Read the prelaunch status

Published templates and verified customer availability remain pending.

A little help with the whole task

A little less busywork.
A little more room for you.

Explore the sample experience while launch details are being finalized.

View pricing status Explore the simulation