zuul
/
zuul-operator
Code Issues Proposed changes

Broaden scope of potential config updates 

Some of the Zuul CRD spec entries may be used to directly write key
values to zuul.conf.  As a result, we need to trigger config updates
when those sections may change.

Change-Id: I5799137043f387553f55ae5fc31ce6b42d2046d8
This commit is contained in:
Michael Kelly 2023-05-18 14:38:04 -07:00
parent b742ca1f79
commit b3e7319314
No known key found for this signature in database
GPG Key ID: 77F7FE93040ECF3E
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
zuul_operator/operator.py
View File

@ -158,8 +158,13 @@ def update_fn(name, namespace, logger, old, new, memo, **kwargs):
if new.get('connections') != old.get('connections'):
logger.info("Connections changed")
conf_changed = True
for key in ['executor', 'merger', 'scheduler', 'registry',
'launcher', 'connections', 'externalConfig',
for key in ['executor', 'merger', 'scheduler', 'web', 'fingergw']:
if new.get(key) != old.get(key):
logger.info(f"{key} changed")
conf_changed = True
for key in ['registry', 'launcher', 'connections', 'externalConfig',
'imagePrefix', 'imagePullSecrets', 'zuulImageVersion',
'zuulPreviewImageVersion', 'zuulRegistryImageVersion',
'nodepoolImageVersion']: