zuul/zuul/cmd
James E. Blair 864a2b7701 Make a global component registry
We generally try to avoid global variables, but in this case, it
may be helpful to set the component registry as a global variable.

We need the component registry to determine the ZK data model API
version.  It's relatively straightforward to pass it through the
zkcontext for zkobjects, but we also may need it in other places
where we might alter processing of data we previously got from zk
(eg, the semaphore cleanup).  Or we might need it in serialize or
deserialize methods of non-zkobjects (for example, ChangeKey).

To account for all potential future uses, instantiate a global
singleton object which holds a registry and use that instead of
local-scoped component registry objects.  We also add a clear
method so that we can be sure unit tests start with clean data.

Change-Id: Ib764dbc3a3fe39ad6d70d4807b8035777d727d93
2022-02-14 10:58:34 -08:00
..
__init__.py Add zuul-scheduler tenant-reconfigure 2022-02-08 14:14:17 -08:00
client.py Make a global component registry 2022-02-14 10:58:34 -08:00
executor.py Add zuul-scheduler tenant-reconfigure 2022-02-08 14:14:17 -08:00
fingergw.py Add zuul-scheduler tenant-reconfigure 2022-02-08 14:14:17 -08:00
manage_ansible.py Remove ununecessary shebangs 2020-05-18 19:10:33 +02:00
merger.py Add zuul-scheduler tenant-reconfigure 2022-02-08 14:14:17 -08:00
scheduler.py Add zuul-scheduler tenant-reconfigure 2022-02-08 14:14:17 -08:00
web.py Add zuul-scheduler tenant-reconfigure 2022-02-08 14:14:17 -08:00