So, I have this ticket to replace the bash scripts we're currently using to publish container images to Fedora's registry and quay.io.

But...looking at this thing...it occurs to me, why have two Python thingies for publishing images to registries? Why not just extend this to also handle container images?

A very rough sketch in my head goes something like:

• Replace the long if/elif/elif... block in handler.py with something a bit more heavy-duty which maps image properties to subclasses of some kinda "image handler" class
• Have an AzureImage class which calls the existing azure() method then runs the playbook, as currently
• Add one or more classes for handling container images

If we want to keep the 'generic' playbook handling we could have a generic AnsibleHandler class or something which AzureImage could inherit from, you know, details details. :P I don't know yet whether ansible is a sensible way to publish container images, but I don't think it is - there's https://docs.ansible.com/ansible/latest/collections/community/docker/index.html , but AFAICS that's very specific to the Docker registry...

Before I go any further working on it, WDYT? Does this seem like a reasonable idea or would you rather keep them separate?

CCing @kevin , @siosm , @pbrobinson for reference.