f260139 has been done to fix the warning throiwn at initialization time.
However this has introduced a regression. When a service is created, the registration flow ends calling register_host which tries to access self.proxy_allowed_hosts which might not be initialized yet, since the initialization is performed only when someone calls get_proxy_allowed_hosts.
We can make proxy_allowed_hosts a setter/getter property. When either of them is accessed we initialize the registry, if not done yet. Basically they replace the logic inside the get_proxy_allowed_hosts method (which can be replaced by the getter).
f260139 has been done to fix the warning throiwn at initialization time.
However this has introduced a regression. When a service is created, the registration flow ends calling register_host which tries to access
self.proxy_allowed_hostswhich might not be initialized yet, since the initialization is performed only when someone callsget_proxy_allowed_hosts.We can make proxy_allowed_hosts a setter/getter property. When either of them is accessed we initialize the registry, if not done yet. Basically they replace the logic inside the
get_proxy_allowed_hostsmethod (which can be replaced by the getter).