Offload run-on-server to a tentacle

[droyad]

The Octopus administrator will be able to configure via the command line the address and thumbprint of a tentacle that will handle run-on-server steps that execute user provided scripts (Script Step, Azure Steps, etc).

This Tentacle can be installed anywhere. It doesn't have to be on the same machine as the Octopus Server.

The next step is to bundle a worker (#4215) to make setting this up easier for users who want the tentacle on the same machine as the server.

This is in interim step towards workers (#4158). When the Workers feature ships:

• If a tentacle is configured using this method:
  • It will be automatically added to the default worker pool
  • The built-in (default) worker will not be enabled
• The command line configuration options for this feature will be removed

Usage

To enable this feature, first setup a Tentacle either on the same machine or another machine. Then run:
Octopus.Server.exe external-worker --address https://example.com --thumbprint ABCD12345

Then restart the server. When you perform a deployment, you should see External Worker appear instead of Octopus Server in the task log headers.

If you run into a problem with this feature, you can turn it off by running Octopus.Server.exe external-worker --reset and restarting (and then letting us know via the support channels).

[matt-richardson]

It's a real pain when command line configuration options are removed - it is effectively our public api. It hurts pretty bad when we're having to code up OctopusDSC.

[droyad]

Hence calling it out up front. The removal will be in a minor release and noted in the release notes. No point keeping the options if they don't do anything/

[matt-richardson]

Hmmm. Maybe in that case it shouldn't go into the DSC. We'll just script it.

[octoreleasebot]

Release Note: Run-on-server script steps can now be run on a Tentacle that runs a under a different user account

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.