A charms.reactive mechanism to replace @hook('upgrade-charm') does not yet
exist. It is tricky because the charm-upgrade code needs to be run before any
of the other handlers (because the other handlers may depend on migration work
having been run). I don't think any designs have been proposed that offer an
advantage over @hook('upgrade-charm'). @hook('stop') is pretty rare, and I
don't think any charms.reactive design work has been done.
--
https://code.launchpad.net/~aieri/hw-health-charm/+git/hw-health-charm/+merge/364750
Your team Nagios Charm developers is subscribed to branch
hw-health-charm:oo-rewrite-integration.
--
Mailing list: https://launchpad.net/~nagios-charmers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~nagios-charmers
More help : https://help.launchpad.net/ListHelp
