fedimg publishes messages when it uploads images. This allows for things like relvalconsumer to update the list of AMI locations in the release validation page, and it would also allow for triggering a test process.
cloud-image-uploader does not currently publish any messages when it runs. It probably should publish either a single message each time it runs, listing out appropriate information on what it uploaded where, or many individual messages split up somehow per image type, remote service, and so on.
I'm inclined to take the many individual messages approach and alter (at a minimum) the topic design from what fedimg does, so we'll also need to go adjust relvalconsumer (and any other consumers) as well.
relvalconsumer
Also as part of this work, the deployment will need to be coordinated with the infra team as we'll need permissions to publish on the topic(s) we select.
Metadata Update from @jcline: - Issue assigned to jcline
for containers maybe we publish a message per manifest? I'm not sure whether we want/need to publish a message per image.
Since we publish messages now, I'm going to close this as done
Metadata Update from @jcline: - Issue status updated to: Closed (was: Open)