Currently, the VPN config is not generated from the template after each upgrade.
For me, it's a bug as we can't propagade changes made to the template during the upgrade.
As I guess all paramaters from the cube file are store as settings in the app, it shouldn't be too difficult?
The downside is that it might break things for people who manually modified their VPN config, and who thought it would never be overridded :/
Steps to reproduce
Just perform an upgrade of the VPN client and note that the config wasn't updated from the config template.
Expected behavior
Well, the config is updated from the config template each time I upgrade the app.
Describe the bug
Currently, the VPN config is not generated from the template after each upgrade.
For me, it's a bug as we can't propagade changes made to the template during the upgrade. As I guess all paramaters from the cube file are store as settings in the app, it shouldn't be too difficult?
The downside is that it might break things for people who manually modified their VPN config, and who thought it would never be overridded :/
Steps to reproduce
Just perform an upgrade of the VPN client and note that the config wasn't updated from the config template.
Expected behavior
Well, the config is updated from the config template each time I upgrade the app.