Reinstate automatic catalogue generation #4
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ideally the catalogue should be regenerated automatically.
Wired: cronjob like we used to have
Inspired: webhook whenever there's a new released version of a recipe
Current status:
git.coopcloud.tech/coop-cloud/abra
, automatically published todev
tag on push (and should make tagged releases whenever we push a tag)drone-abra
Drone plugin is up-to-date as well (still needs moving to git.coopcloud.tech from Docker Hub tho)auto-apps-json
is renamed toauto-recipes-catalogue-json
, and configured to do a Drone build to generate and publish the catalogue (example) -- it's currently pushing to atesting
branch inrecipes-catalogue-json
.TODO:
recipes-catalogue-json
showing up as from me? (Example). Drone is authenticating using a key added to theabra-bot
repo, shouldn't it show up asabra-bot
? Or maybe Drone is picking up git "author" settings from the source repo (in this case,auto-recipes-catalogue-json
)collabora
(and many other recipes) have switched from a digest to"unknown"
. Or maybe this isn't too critical, as the image digests seem to be changing upstream anyway 🙄auto-recipes-catalogue-json
build whenever there's a new release of a recipe? Ideally it'd be nice to avoid needing to add to.drone.yml
in all the recipe repos; maybe a global webhook linked up to something? (n8n
? ducks). This might become easier if all the recipes are in a separate organisation, see coop-cloud/organising#377.Did you create the key while authenticated as yourself? Typically you have to create a seperate user and create a key once logged in with it
thanks for the reply @mayel!
I generated a new SSH key using
ssh-keygen
and added it to theabra-bot
user on Gitea.I think this is related to coop-cloud/organising#368 and it is caused by a rate limit.
Thanks @moritz! I thought the
docker login
step would fix that, but perhaps it only gets us a higher rate limit, which still isn't high enough to look up all the images in the catalogue?I agree with the comment by @decentral1se on Matrix, though:
Maybe we just drop digest generation entirely, for now?
coop-cloud/organising#379
I feel like if we had a Not Gnarly way to template the
.drone.yml
files for all recipes from a central repository, then it wouldn't be too bad? We already have this config for the recipe CI, so adding a separate stanza for per-tag catalogue generation doesn't seem too bad? I think we can get inter-repository webhooks going, so when a tag gets pushed to a recipe repo, it pings the catalogue generation repo. It's drone plugins somewhere afaicr.Oh yeah forgot to update here, another mass-borking later, and we're already doing this, using the Drone
downstream
plugin, e.g. for vaultwardenCould maybe close this off now? It's pretty automagic again.
🤟
@moritz open again 🙈