On Wed, Aug 31, 2016 at 3:20 PM, Robert Mayr <robyduck(a)fedoraproject.org> wrote:
2016-08-31 17:00 GMT+02:00 Adam Miller
> Hello all,
> It was requested from members of the Fedora Cloud WG that we
> provide a persistent URL that will always offer up the latest Two Week
> Atomic Host release from Fedora.
> Initially I wrote some code that would handle this in the Two Week
> Atomic script but dgilmore brought up a good point that this
> removes our ability to easily track what compose any given "latest"
> image downloaded at various points of time actually is since it would
> overwrite the images in-place (we could maintain a listing of
> checksums but that's not ideal). What was then proposed and I like
> better is to offer a web endpoint that would do two things:
> 1) Serve up the latest image for the different image types (something
> like getfedora.org/atomic/latest/$IMAGE_TYPE
> 2) A simple URL endpoint that would return the actual image name that
> is the 'latest' for use by people who want to write scripts to
> automate and verify the images. (something like
> The needed data is already provided via fedmsg by the Two Week Release
> and is used to populate download links for the Atomic page so
> hopefully this won't be too much work. I'm also willing to do the work
> and just submit the code for review but would like some guidance and
> feedback on the topic in general.
> Thank you,
>  -
>  - https://getfedora.org/en/cloud/download/atomic.html
> websites mailing list
I think this is very specific and would be used by just a few people, but I
might be wrong.
Adding this kind of images just for scripting is probably too much for a
website which is a brochure website. I would rather host them somewhere
else, if you need to have a static URL which always has the latest image.
Getfedora has them, and it's good to keep them with the whole path, date
I would also like to see what the plan is for Atomic, because if we need to
rewrite the cloud pages because Atomic is going to be primary, then we
should not write anything before this happens, IMHO.
If this isn't something that should be done with the website, then we
might be able to handle with