Change Details

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 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 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