config-changed should be invoked after charm upgrade
Bug #919745 reported by
Kapil Thangavelu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
after a charm is upgraded its configuration values/defaults may have changed, and the config-changed hook (idempotent) should be called after the upgrade hook so a service unit has a chance to respond to any configuration changes.
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| Changed in juju: | |
| importance: | Undecided → Medium |
| Changed in juju: | |
| status: | New → Triaged |
| Changed in juju: | |
| importance: | Medium → Low |
| summary: |
- config-changed should be invoked after upgrade + config-changed should be invoked after charm upgrade |
To post a comment you must log in.
I've recently been writing this as my default upgrade-charm hook:
#!/bin/sh
set -e
home=`dirname $0`
$home/stop
$home/install
$home/config-
$home/start
Seems like that would be the logical workflow for all upgrades to take... I've never really understood having a separate upgrade-charm hook.