Jeremy Stanley wrote:
On 2020-08-03 15:37:01 +0200 (+0200), Thierry Carrez wrote: [...]
I suspect removing the tenant is as simple as clearing out the tenant definition in project-config:zuul/main.yaml. However there might be a catch-22 there for the retirement of kata-containers/zuul-config.
Luckily it shouldn't be, since kata-containers/zuul-config is a trusted config project and therefore its retirement change won't be speculatively executed (as you note below).
I was thinking about these steps:
1- Push a closing commit to kata-containers/zuul-config (that will remove the job definition for zuul-config itself, but IIRC config projects are not self-testing, so this should work ?)
2- Rename kata-containers/zuul-config to x/kata-zuul-config to clear out the namespace from https://opendev.org/explore/organizations (or should it just be left in place?)
I would skip this step, it needs a maintenance window for Gerrit downtime anyway, and could always be performed after removal if it becomes a source of confusion. The retirement readme in step 1 can always link to Kata's org on GitHub to hopefully eliminate that.
3- Remove the katacontainers tenant definition from project-config:zuul/main.yaml (or should that be run before (2)?)
[...]
It's entirely independent of step 2, so doesn't matter either way.
Thanks,
I proposed https://review.opendev.org/#/q/topic:retire-kata-tenant