Backwards incompatible change to config.changed states

[Stuart Bishop]

On 23 April 2016 at 04:02, Cory Johns <cory.johns at canonical.com> wrote:

> Is anyone depending on the current behavior?  Are there any objections to
> this change?

I can argue both designs, but think that the most useful one is what
you are proposing (config.changed not being set in the first hook,
which is not necessarily the install hook).

If you are clarifying this, you should also clarify how things work in
the upgrade-charm hook when new config options are added or removed.

Your proposed change does not affect my work, and will allow me to
simplify some things.

-- 
Stuart Bishop <stuart.bishop at canonical.com>