I have a similar question to a previous unsolved one, but with a proposed solution that would require new functionality by the Octopus team.
We have a requirement to optionally run our service in a local user account, in order for our application to have access to the local users files.
When using our own installer we solved this problem by not reinstalling a service if it was already there,
but now we would like to reproduce this solution with octopus deploy
The installer naturally doesn’t have access to the local users password, so what we did for a brand new install is just install as a local service .
But if the user requires local file access, they can manually (or through our application) change the service to run as the local user.
If somehow, the octopus service deployment can reuse the existing service setup, any updates would not require the users password.
I notice that octopus deploy installs the service every release to use the executable in a new release directory.
perhaps if symbolic links were used such that the service path could remain constant the service could then be restarted rather than recreated leaving any configuration unchanged
This would be a very good feature for octopus deploy to be able to do, allowing service configuration to optionally be sticky (if needed)
If this is not practical, i think we will have to somehow do the service setup by our application.
I will attempt to do the symbolic link approach and manually install/update the service
Thanks for your help!