I don’t think this is an Octopus failure, I believe this is an issue related to Tentacle permissions, however it would be great to find a resolution or workaround.
- We are currently running Octopus Tentacles using default configuration, i.e. running under System account. We would like to keep them this way.
- We want to write a script to set up an application (Logstash) as Windows service using NSSM (Non-Sucking Service Manager). It’s no brainer doing it manually, but we want to automate it.
If a script starts a NSSM process that tried to configure Logstash as a service, the deployment hangs
If I try change Start-Process parameters to accept -Verb RunAs option, then deployment completes, but then I don’t seem to be able send required arguments to NSSM together with RunAs option.
So I wonder if anyone has been through similar problems and whether you managed to solve them.
Thanks in advance