Previously, TraefikRouteProvider did not send any information back to TraefikRouteRequirer, including the external_host Traefik may be bound to, so the Requirer has no way of knowing (inside the Juju data/permissions model) what external address it could be reachable on.
Now, TraefikRouteProvider keeps the "known" external_host in StoredState, and checks traefik-k8s's external_host property at instantiation. If it differs, it writes this to relation data, and an event is fired from the Provider, so the charm which has provided the configuration can read an external_host property.
Previously,
TraefikRouteProvider
did not send any information back toTraefikRouteRequirer
, including theexternal_host
Traefik may be bound to, so theRequirer
has no way of knowing (inside the Juju data/permissions model) what external address it could be reachable on.Now,
TraefikRouteProvider
keeps the "known"external_host
inStoredState
, and checkstraefik-k8s
'sexternal_host
property at instantiation. If it differs, it writes this to relation data, and an event is fired from theProvider
, so the charm which has provided the configuration can read anexternal_host
property.