You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
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 :
"major" (0 for example) : this is the latest image version for the major version 0
"major.minor" (0.25 for example) : this is the latest version the the minor version 0.25
Why is this needed?
With these two new tag type, it becomes possible to :
If using "major" tag : fix the major version and ensure it is up to date, with all minor update and patches. The update is automatic as with "latest" but we ensure the container is not updated to another major version
If using "major.minor" tag : fix the minor version and ensure it is up to date, with all the patches applied.
The text was updated successfully, but these errors were encountered:
Hey there!
While I agree this would be useful, in production prefer to pin the version, to ensure the exact image is used.
For example smallstep/step-ca:0.25.0@sha256:9cdef9c9daecf71d87d23d83a57712867e6c08d4f9ecad998d4bc6239f2218dd
Thank you for your reply.
I understand this could be the recommended approach, but why would you prefer this to pining 0.25 tag for example ?
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: