Looks like a good start to me.

A few things I wonder about:

• Do we need to prune images ever? would this be something to add to this app? Or something seperate?

• We probably should sometime have a larger conversation on if we want to add a QE step in here. ie, do we want to test and only upload passing images? or do we want to upload everything, but somehow 'tag' images that pass? But I am not sure at all how people search for images on Azure...

But I'm fine merging this as is and expanding on it/discussing those things somewhere else.

Looks like a good start to me.

A few things I wonder about:

• Do we need to prune images ever? would this be something to add to this app? Or something seperate?

Yes, that's next on my to-do list and I've got a few ideas, but nothing I've quite committed to just yet so I didn't document anything. I'm currently leaning towards having a Function run in Azure that just runs once a day/week/whatever and implements the pruning rules. We can write it as a Python function and maybe even ensure it exists via Ansible, or just set it up one-time manually if that's not easy/possible.

• We probably should sometime have a larger conversation on if we want to add a QE step in here. ie, do we want to test and only upload passing images? or do we want to upload everything, but somehow 'tag' images that pass? But I am not sure at all how people search for images on Azure...

Indeed. The way it currently works is all the images are marked with a flag to "exclude them from latest" so the only way to use them is to explicitly boot the image ID, which we don't link to. You can then flip that flag to expose them as the latest (assuming they sort higher, semver-wise, I think). For the super short term I'm going to handle promoting them manually, but I'm definitely motivated to automated that process.

The service now cleans up Azure images, so I've documented that in the SOP.

Lets get this merged.