Change Details

This should ease the scheduling of a new forge: - on staging, this will list a subset of disabled origins - on production, this will register a recurring task to list a forge So, the following would be enough to list appropriately in staging/production: ``` swh scheduler add-forge-now \ register-lister \ list-gitea-full \ ( --production | --staging \ # to list only enabled | disabled origins ) url=https://git.afpy.org/api/v1/ ``` TODO: probably rewrite the current passing test to something a bit more elaborate Related to https://gitlab.softwareheritage.org/infra/sysadm-environment/-/issues/4674

This will ease scheduling of new add-forge-now requests, on: - staging: this will list a subset of disabled origins once - production: this will register recurring tasks (full, incremental if any) to list that new forge So, the following would be enough to list appropriately in staging/production: ``` swh scheduler add-forge-now \ ( --production | --staging \ # to list only enabled | disabled origins ) register-lister \ gitea \ url=https://git.afpy.org/api/v1/ ``` Related to https://gitlab.softwareheritage.org/infra/sysadm-environment/-/issues/4674

This shouldwill ease the scheduling of a new add-forge:e-now requests, on: - on- staging,: this will list a subset of disabled origins once - on- productionn: this will register recurring tasks (full, this will register a recurring task to list aincremental if any) to list that new forge So, the following would be enough to list appropriately in staging/production: ``` swh scheduler add-forge-now \ ( --production | --staging \ # to list only enabled | disabled origins ) register-lister \ list-gitea-full \ ( --production | --staging \ # to list only enabled | disabled origins )a \ url=https://git.afpy.org/api/v1/ ``` TODO: probably rewrite the current passing test to something a bit more elaborate Related to https://gitlab.softwareheritage.org/infra/sysadm-environment/-/issues/4674