da33bf35cb0c9a2eb63e149261d459bad2b9c2dd
It seems families should only have images of a single architecture in them, rather than being a container for multiple architectures of the same release. Swap the arch suffix from the image name to the image family.
See also: https://pagure.io/cloud-sig/issue/438
LGTM. Thanks!
:thumbsup:
Pull-Request has been merged by jcline
Unfortunately this doesn't work: 409 POST https://compute.googleapis.com/compute/v1/projects/fedora-cloud-devel/global/images?requestId=f0a25b91-4f6b-c781-a4f5-11cddf417aca: The resource 'projects/fedora-cloud-devel/global/images/fedora-cloud-42-1-1' already exists
409 POST https://compute.googleapis.com/compute/v1/projects/fedora-cloud-devel/global/images?requestId=f0a25b91-4f6b-c781-a4f5-11cddf417aca: The resource 'projects/fedora-cloud-devel/global/images/fedora-cloud-42-1-1' already exists
Surprisingly, it seems that the image name needs to be unique across families, so I'll just tack the arch on again. I'm guessing this particular resource layout is because whenever it was designed more than one architecture wasn't top of mind.
Ah, yes. Sorry, the image name does need to be unique in the resource model.
It seems families should only have images of a single architecture in
them, rather than being a container for multiple architectures of the
same release. Swap the arch suffix from the image name to the image
family.
See also: https://pagure.io/cloud-sig/issue/438