Comment 1 for bug 1866171

Is there any reason in particular this doesn't fall into the normal use of the juju wait plugin to make changes, then wait for them to settle vs needing it on a single specific call? My concern is that a config-change could trigger different relation updates and such but it would be a bit of a "false promise" that it's "done".