I need some help with understanding the best way to manage relation info across an application's lifecycle with the reactive framework.
I'll start with the situation that brings me here: I have a reactive charm that provides some fairly static relation info: nagios checks over the nrpe-external-master interface. This charm is deployed and related to the nrpe subordinate. My charm adds the nagios checks it supports when joining the relation, and removes them when it departs. Now, in a new version of my charm, I want to add or remove these nagios checks, which means I need to change the relation data. What is the best way to do this with the reactive framework? It would be ideal to trigger a "conversation" to happen, that would use the same relation state handlers I already have in my charm, but I'm not sure how to do this. I could see a similar situation for other interfaces. http, for example, where you have to set extra info in YAML strings for load-balancing with apache2 and haproxy. It's easy to imagine needing to change those parameters across charm upgrades over time. I'm trying to avoid the brute-force option, which is to destroy and re-add the relation. That works, but seems heavy-handed and wrong. -Casey
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
