snappy config command does not restart service after setting the configuration

[Simon Eisenmann]

The docs for snappy config command at https://developer.ubuntu.com/en/snappy/guides/config-command/ says: "When the configuration is applied the service will be restarted by snappy automatically."

Though the service does not get restarted. Spreed WebRTC just got a configuration and then it is applied with `snappy config spreed-webrtc /tmp/spreed-webrtc.yaml` the service is not restarted by snappy.

To test yourself with spreed-webrtc (on armhf):

sudo snappy install spreed-webrtc
sudo snappy config spreed-webrtc > /tmp/spreed-webrtc.yaml
# Now modify something (eg the ports)
sudo vi /tmp/spreed-webrtc.yaml
sudo snappy config spreed-webrtc /tmp/spreed-webrtc.yaml

This is problematic, as there is no way to restart a snap provided service easily when you just know the name of the snap. One needs to know the systemd service name which is complicated.

[Chad Miller (cmiller)]

Within new configuration hook, this may could be

snapctl reload appnameinyaml

[Samuele Pedroni (pedronis)]

This doesn't quite apply to the new snap configuration implementation for UC 20 or later.

[Samuele Pedroni (pedronis)]

I mean UC 16