Avoid removing Stork user on update
The issue was reported on the mailing list by Bertrand Buclin on 2022-09-21.
Another annoying thing with the current installation scripts is that it removes the stork-agent (and stork-server for the server) username at every upgrade. For the agent, the post installation scripts has logic to add the re-created stork-agent user to the bind group so that I can access the Bind files, but it does not do the same for the _kea group, and one has to always add the stork-agent user manually after the upgrade. Delete and adding also has the undesired side effect that the UID and GID may change at each release.
Would it be possible:
- not to delete the stork-agent (or stork-server) user if this is an upgrade: it is already in place, so no need to change things, nor cause a change in UID and GID
- enhance the install script to also add stork-agent to the _kea group (after testing of course that Kea is also installed on the system)