Ben Hoyt

We discussed this at the sprint today with the Juju team, and their suggested approach (and what OpenStack does) is to get this via network-get ingress addresses for the peer...

Leaving open for now -- should be considered in the context of charm libraries and "components".

This relates to the ongoing discussion about holistic ("one event handler to rule them all") vs delta-based charms, which we're going to discuss further and try to determine some direction...

I think my previous comment is still a good summary here. This is closely related to the "holistic" event handling pattern, which we're going to document more clearly and make...

This is an interesting idea, but I don't think there's enough of this happening for anything formal or automated. We're pretty careful and curated about what we include in /...

Part of this is a Juju bug -- which will be handled with the upcoming Pebble Notices (aka Pebble Events) feature. From the OF side, you can run ./dispatch with...

I think we can probably improve our docs here in places, however, I think it's probably better that the details are described in the Juju docs rather than in the...

@tmihoc You had some thoughts about making Juju event docs clearer -- what was your concrete plan for that again?

Going to close this won't-fix for now as people aren't clamouring for it (reopen with more info if you disagree). In terms of your own IP address, you can call...

Arguably we should do the dynamism using an instance, but we're probably not going to change that at this point. `Harness.begin` "solves" this by dynamically inheriting from the charm class.