As a user I can have repo with immutable tags
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 56
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 22
Description
Author: @ipanova (ipanova@redhat.com)
Redmine Issue: 7805, https://pulp.plan.io/issues/7805
https://docs.mirantis.com/docker-enterprise/v2.1/dockeree-products/dtr/dtr-user/manage-images/prevent-tags-from-being-overwritten.html
Prevent tags from being overwritten
By default, users with read and write access to a repository can push the same tag multiple times to that repository. For example, when user A pushes an image to library/wordpress:latest, there is no preventing user B from pushing an image with the same name but a completely different functionality. This can make it difficult to trace the image back to the build that generated it.
To prevent tags from being overwritten, you can configure a repository to be immutable. Once configured,it will not be possible for anyone else to push another image tag with the same name.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating repository configuration and the image-tag push path, then read nearby tests for repository updates and tag overwrites. Done means a repository can be configured as immutable and attempts to overwrite an existing tag are prevented, with coverage for both immutable and default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100