2021-12-20 06:39:00 <terra> i
2021-12-26 22:01:34 <tomalok> ikke: when you have a chance, could you make https://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images publicly viewable?
2021-12-27 11:54:35 <ikke> tomalok: done
2021-12-27 17:09:06 <tomalok> ikke: thx!
2021-12-28 17:03:40 <tomalok> FYI - identified an issue with the latest batch of AWS images (https://gitlab.alpinelinux.org/alpine/cloud/alpine-cloud-images/-/issues/126) -- i have a fix, though we'll need to build and publish new images.
2021-12-28 17:06:40 <tomalok> ikke: with alpine-ec2-ami repo being retired, need to find a place to put the interim source YAML for the cloud images page...  would it make any sense to simply update that file in alpine-mksite until we have an operational cloud image service?
2021-12-28 17:07:41 <ikke> I think that should not be an issue, just like we keep the releases.yaml file already there now
2021-12-28 17:09:09 <tomalok> i should be able to wire that up, if you have a preference whereabouts the file should live?
2021-12-28 17:11:56 <ikke> Probably in the cloud folder
2021-12-28 17:15:04 <minimal> ikke: "store it in the cloud"? ;-)
2021-12-28 17:15:18 <ikke> yes ;-)
2021-12-28 17:15:42 <ikke> s/cloud/someone else's computer/ :P
2021-12-28 17:16:45 <tomalok> far as i can tell that folder ends up being the contents of https://alpinelinux.org/cloud -- would this also cause the raw yaml to be available in that dir?
2021-12-28 17:19:08 <ikke> It copies specific files to the _out dir which is what will be copied to the public www dir
2021-12-28 17:20:29 <tomalok> Maybe following the alpine-releases.conf.yaml pattern - top level of the repo, only referenced in the Makefile (where the current cloud releases url is, too)
2021-12-28 17:21:03 <ikke> counterpoint is that releases.json lives in /
2021-12-28 17:21:15 <ikke> https://alpinelinux.org/releases.json
2021-12-28 17:22:04 <ikke> for the conference, I've put everything in conf/
2021-12-28 17:24:39 <tomalok> the existence of this YAML file should be temporary -- if someone starts depending on the existence of the file and then we switch to the cloud image service and no loner need to maintain the old yaml...
2021-12-28 17:25:31 <tomalok> but if the yaml isn't specifically copied to _out, that shouldn't be an issue, if i read that correctly
2021-12-28 17:36:30 <tomalok> i'm assuming the current auto-regenerate trigger probably will need to be adjusted too?
2021-12-28 17:43:17 <ikke> Right now it downloads the yaml from https://gitlab.alpinelinux.org/alpine/cloud/alpine-ec2-ami/-/raw/master/releases/alpine.yaml
2021-12-28 17:43:24 <ikke> and puts that in the cloud/ dir
2021-12-28 17:43:33 <ikke> and the lua script uses that to generate the final page
2021-12-28 17:43:49 <ikke> I think the only change is that it no longer has to download that file
2021-12-28 17:44:06 <ikke> for the rest, everythign can stay the same (or I must be misunderstanding something)
2021-12-28 17:49:03 <tomalok> basically just cutting out the middle steps from the Makefile
2021-12-28 17:50:12 <tomalok> will the commit/merge to alpine-mksite be sufficient to trigger the rebuild of https://alpinelinux.org/cloud ?
2021-12-28 17:52:00 <ikke> Right now ther is an explicit make command that needs to be run
2021-12-28 17:52:14 <ikke> So it should be made part of the regular build process
2021-12-28 18:26:41 <ikke> tomalok: I think you should put cloud/releases-in.yaml as the makefile expects
2021-12-28 18:26:57 <ikke> The target that downloads that file can then be removed
2021-12-28 19:42:16 <tomalok> ikke: yeah there's a chain reaction of things happening, sounds like that'd be the least disruptive way forward...  new images built & tested, publishing them to all the regions now...  looks like there's a new region in Jakarta, too.
2021-12-28 19:45:38 <tomalok> heh, .gitignore filteres out releases*.yaml
2021-12-28 19:46:02 <ikke> Yes, because right now it's generated
2021-12-28 19:46:05 <ikke> but you can remove that rule then
2021-12-28 19:47:12 <tomalok> downloads/releases.yaml is still a thing, for instance
2021-12-28 19:47:39 <ikke> yes
2021-12-28 19:47:44 <tomalok> i can have an explicit !cloud/releases-in.yaml rule
2021-12-28 19:47:57 <ikke> oh, it was a global rule
2021-12-28 19:48:02 <tomalok> yeah
2021-12-28 19:58:14 <tomalok> update-cloud: \n\t rm cloud/releases-in.yaml \n\t $(MAKE) - remove this whole Makefile target or just keep the $(MAKE) part of it? 
2021-12-28 20:12:19 <ikke> I think we can just remove it
2021-12-28 20:12:43 <ikke> That's the target that is executed by the webhook
2021-12-28 20:13:26 <ikke> But the cloud page would now be updated by the general site update process (ie, when we push a new commit to master / production)
2021-12-28 20:30:14 <tomalok> ikke: https://gitlab.alpinelinux.org/alpine/infra/alpine-mksite/-/merge_requests/35
2021-12-28 20:58:28 <tomalok> ikke: thx for the approval, but i don't have merge powers in alpine/infra ;)
2021-12-28 20:58:46 <ikke> I'm aware :-)
2021-12-28 20:59:29 <tomalok> ok, just making sure you weren't just leaving that part to me :)
2021-12-28 21:19:28 <ikke> tomalok: Does this look good? https://wwwtest.alpinelinux.org/cloud/
2021-12-28 21:21:43 <tomalok> ikke: looks like it worked -- it's got the new region and everything looks like it's in place
2021-12-28 21:21:50 <ikke> cool
2021-12-28 21:26:26 <ikke> pushed
2021-12-28 21:43:39 <tomalok> ikke: tyvm!