OCI: support tag names
Bug #1897813 reported by
Andreas Hasenack
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
When pushing an image to a registry, it looks like launchpad defaults to the "edge" tag name. This bug is two-fold I guess:
a) support arbitrary names in the push rule. Something like "repo/name:tag". This would mean that the image that lp just build would have to be retagged with "<tag>" before the push, or have some other way of requesting the tag name from the user prior to the build
b) support dynamic tags, for versions. Much like a deb build recipe has a version and adds it to d/changelog, we could want to have a version number as the tag, and push that to the registry.
Changed in launchpad: | |
importance: | Undecided → Critical |
status: | New → Triaged |
tags: | added: oci |
Changed in launchpad: | |
importance: | Critical → High |
To post a comment you must log in.
We'd also be very interested in this as we have some charms where application version upgrades are driven by changing the image location, so we'd like to be able to deploy `appteam/app:v1` and then trigger a version upgrade by changing to `appteam/app:v2` for instance. Having these created via the OCI recipe would be extremely useful.