snappy config command does not restart service after setting the configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Won't Fix
|
High
|
Unassigned |
Bug Description
The docs for snappy config command at https:/
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-
To test yourself with spreed-webrtc (on armhf):
sudo snappy install spreed-webrtc
sudo snappy config spreed-webrtc > /tmp/spreed-
# Now modify something (eg the ports)
sudo vi /tmp/spreed-
sudo snappy config spreed-webrtc /tmp/spreed-
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.
Changed in snappy: | |
status: | New → Triaged |
importance: | Undecided → High |
Within new configuration hook, this may could be
snapctl reload appnameinyaml