Currently we use maintain_harbor to create the projects for all the users at once and keep them up.
We should move the creation to the builds-api, when you start a new build.
That way we can skip creating *all* the projects beforehand, and depending on a separated process to do so.
We can still use maintain_harbor for the cleanup (that we don't yet do xd)
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| builds-api: create the harbor project beforehand if it does not exist | repos/cloud/toolforge/builds-api!34 | raymond-ndibe | create_harbor_project | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | bd808 | T133777 Tools that should get archived/deleted (tracking) | |||
| Resolved | Andrew | T170355 Figure out process for deleting an unused tool | |||
| In Progress | Andrew | T332514 Store state information for the disable tool process outside NFS | |||
| Resolved | dcaro | T342563 [harbor] Stabilize the current installation | |||
| Resolved | Raymond_Ndibe | T337386 [builds-api.start] Create the harbor project beforehand if it does not exist | |||
| Open | None | T334629 Update maintain_kubeusers to use the toolstate database | |||
| Resolved | dcaro | T334585 [cookbooks.wmcs.toolforge.component.deploy] Add secrets support when deploying | |||
| Resolved | dcaro | T304532 buildservice: migrate to helmfile from of kustomize |
dcaro merged https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-api/-/merge_requests/34
builds-api: create the harbor project beforehand if it does not exist