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
Right now in OCP we're pushing the rhel-9.6 image to both Quay.io and registry.ci using the new capabilities added in #1091. The problem is that the cosa schema only supports specifying a single pushed repository. But ideally we include all of them and not just the last one in the list (which is what currently happens).
I think probably the cleanest, even though it's still awkward, is to add a primary-image object to the schema which sources the image object's properties, but also adds a new additional-images property. This property is then a list type of image objects.
And then in cosa push-container-manifest, if the primary object already exists for the image we're pushing, add it to the additional-images list in that object instead.
The text was updated successfully, but these errors were encountered:
Unfortunately, we can't change existing types because it would render existing meta.jsons invalid. We'd have to do a schema version bump, which doesn't seem worth it.
Right now in OCP we're pushing the rhel-9.6 image to both Quay.io and registry.ci using the new capabilities added in #1091. The problem is that the cosa schema only supports specifying a single pushed repository. But ideally we include all of them and not just the last one in the list (which is what currently happens).
The relevant part of the schema is here: https://github.com/coreos/coreos-assembler/blob/837190dffb5d5cc56b9815ff937a6196eeb4205e/src/v1.json#L50-L87.
I think probably the cleanest, even though it's still awkward, is to add a
primary-image
object to the schema which sources theimage
object's properties, but also adds a newadditional-images
property. This property is then a list type ofimage
objects.And then in
cosa push-container-manifest
, if the primary object already exists for the image we're pushing, add it to theadditional-images
list in that object instead.The text was updated successfully, but these errors were encountered: