Skip to content

Feature: Requirement of retag the ECR images #6707

@kamal-devtron

Description

@kamal-devtron

🔖 Feature description

The current CI/CD pipeline pushes Docker images to Amazon ECR with a specific tag. However, in many use cases, there's a need to retag existing ECR images without rebuilding or re-uploading them—for example, when promoting an image from development to staging or production environments. Retagging helps maintain version traceability, environment segregation, and audit workflows.

🎤 Pitch / Usecases

Image Promotion: Promote an image from dev to prod by adding a new tag like production to an existing image digest.
Compliance and Audit: Maintain multiple tags (e.g., version numbers, release names) pointing to the same image digest to track deployments and meet compliance requirements
As Base Image: Using the build image as the base image of another Dockerfile

🔄️ Alternative

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Metadata

Metadata

Labels

enhancementNew feature or requestneeds-triageIssue is not approved or ready-to-work on

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions