Appliance breaking changes


I publish the Mosquitto snap, which is used as one of the Appliance images. The project recently released version 2.0, which has some behaviour changes that mean updating to it will require config file tweaks for some people before clients will be able to connect again. This should only affect people who haven’t configured security on the broker.

I’m keen to push the upgrade in the least disruptive way. At the moment I’ve got the new version solely in the edge channel. I’ve already got a 1.6 track which will stay on 1.6.x (the previous version) so even for new installs people will be able to get that version if they need it for some reason.

Along with being able to roll back to a previous version easily, that makes the pain of a broken install at least reduced, but I wondered if you had any thoughts about the best way to handle this.