As of today each lister has its own db. This is mostly irrelevant as they use one table each (except for lister-debian).
This however is a pain in the neck to deploy.
In regards to db creation for example.
- [x] Stop lister/loader-debian services
- [x] Change this to merge all dbs into one (swh-lister)
- [x] Grant guest user read-only access
- [x] Unify the rights to the one user `swh-lister` (with write permission)
~~- [ ] Rename swh-lister to swhlister (and figure out why connection refuses to work with swhlister as user)~~
- [x] Keep swh-lister for now
- [x] Adapt puppet manifests accordingly
- [x] D1518: Adapt swh-lister's base code logic to deal with merged credentials
- [x] Adapt credentials to target the new merged db
- [x] D1519: Merge systemd service into 1
- [ ] Deploy changes on production
- [x] worker01 -> happy
- [ ] other workers
- [ ] Start back lister/loader-debian services
- [ ] Drop old dbs (lister-github, lister-pypi, lister-npm, lister-gitlab, ...)
- [ ] Update the db inventory doc