-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "major" and "major.minor" version tags on docker images #1594
Comments
Hey there! |
Hi ! Thank you for your reply. In my case, as described in the issue, this would be very useful. A lot of organizations that ship official docker images use this approach, it would be great if step-ca could provide that to. Do you plan on adding the tags the near future ? If I can contribute in any way to speed up the process, feel free to poke me ! |
Hello!
Issue details
I am using the step-ca docker image in production.
I do not want to use the "latest" tag, to prevent updating the containers to a major version (with breaking changes) by accident.
Today, I have to tag the exact version (major.minor.patch) and manually updating it each time there is a new version.
It would be great to have "major" and "major.minor" tags on docker hub to make maintenance more convenient.
Today, version tags on docker hub only uses full version of semantic versioning : major.minor.patch (0.25.0 for example)
It would be great to have the following tags :
Why is this needed?
With these two new tag type, it becomes possible to :
The text was updated successfully, but these errors were encountered: