Re: Cloud Image Finder rewrite - now live at image-finder.debian.net

[Arthur Diniz]

On 17/01/2026 13:30, Noah Meyerhans wrote:

On Fri, Jan 16, 2026 at 11:46:40PM +0000, Arthur Diniz wrote:

So I decided to start fresh with a new implementation [2] written in golang,
keeping things minimal and focused on what actually matters. The goal was to
make it functional, future-proof, and easy to maintain over time.

The project is live and ready to use at https://image-finder.debian.net

Wow. From the outside anyway, it looks great! The UI is nice and
performant.

Thanks for the feedback!

A couple bits of feedback:

1. The canonical location of the cloud image downloads is
    cloud.debian.org, not cdimage.debian.org.  Please update references
    accordingly, e.g. the Download link on
    https://cloud-image-finder.debian.net/i/debian-13-ec2-amd64-20260112-2355

Update done: https://salsa.debian.org/cloud-team/cloud-image-finder/-/commit/73293fd0acadfa51ab64a618598688cdd9e2b256

2. For the commercial cloud providers where we publish images, very few
    people will want to use the Download links.  They'll most likely want to
    use the provider's interfaces to launch VMs, etc.  It would be good to
    link to provider-specific resources for this.

    So for example, when the vendor is azure, we should like to resources
    like https://wiki.debian.org/Cloud/MicrosoftAzure and
    
https://azuremarketplace.microsoft.com/en-us/marketplace/apps/debian.debian-13?tab=PlansAndPrice.
    For EC2, we should link to https://wiki.debian.org/Cloud/AmazonEC2Image
    (or even https://wiki.debian.org/Cloud/AmazonEC2Image/Trixie, as
    appropriate) and
    
https://aws.amazon.com/marketplace/seller-profile?id=4d4d4e5f-c474-49f2-8b18-94de9d43e2c0&ref=dtl_prodview-63gms6fbfaota

You can check examples like:

I agree with this idea of having commercial providers information, so I went ahead and implemented a card when providers are Azure or ec2(AWS). - https://cloud-image-finder.debian.net/i/debian-13-azure-amd64-20260112-2355

- https://cloud-image-finder.debian.net/i/debian-13-ec2-amd64-20260112-2355



https://salsa.debian.org/cloud-team/cloud-image-finder/-/blob/main/app/provider-config.json

The content presented in that card is stored in a JSON file so we need to keep that updated if a link change.

3. Rather than a cron job on a fixed schedule, consider how we could
    incorporate content updates into the publication pipeline to reduce to
    refresh latency.  The pipelines are defined at
    https://salsa.debian.org/cloud-admin-team/debian-cloud-images-daily and
    https://salsa.debian.org/cloud-admin-team/debian-cloud-images-release
    Additional executables should be added to the main debian-cloud-images
    project, which is shared by the -daily and -release projects.

I will try to work on that over the next few weeks.

Would be nice having the pipeline publishing to cloud-image-finder but I also like to have a way to back populate the database using cloud.d.o in case something fail in the pipeline. So the optimal solution would be both, having the pipeline pushing and cronjob making sure nothing is missing. Since image-finder is now using OpenSearch, we could have a stage in both pipelines (daily, release) that could do a simple curl command posting the image metadata payload to OpenSearch.

4. In the Search filters, you mis-spelled UUID as UID. That had me
    totally confused for a minute.

This is not misspell is just the same key stored in the metadata JSON published to cloud.d.o. You will be able to see uid in https://cloud.debian.org/cdimage/cloud/trixie/20260112-2355/debian-13-ec2-amd64-20260112-2355.json

noah

OpenPGP_signature.asc
Description: OpenPGP digital signature