Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add spaces support to Tentacle #5239

TomPeters opened this issue Jan 25, 2019 · 2 comments


Copy link

commented Jan 25, 2019

The following commands now take in a space parameter:

  • register-with
  • register-worker
  • deregister-from
  • deregister-worker
  • show-configuration

The deregister-from and deregister-worker commands no longer remove trust for the server. This no longer makes sense when the Tentacle is registered against multiple spaces. Instead if you want to remove trust you should invoke 'Tentacle.exe configure --remove-trust=...'.

When you pass in the space name as the space parameter, the command will look up the space by name and set this as the context for the space-based part of the command. If the name is omitted, then the default space will be used, unless the default space is disabled, in which case it will fail.

The poll-server command has also been updated, but the CLI parameters have not changed. It used to require data which is now space specific. It felt wrong for it to now require a space parameter because the command operates at a server level. It now matches using the servers thumbprint which is obtained using a system level API endpoint.

The Tentacle Manager UI has been updated so that the user picks a space when configuring their machine.

Everything continues to work in a backwards compatible way with pre-spaces versions of octopus (pre 2019.1.0)


@TomPeters TomPeters added this to the 2019.1.0 milestone Jan 25, 2019
@TomPeters TomPeters self-assigned this Jan 25, 2019

This comment has been minimized.

Copy link

commented Jan 25, 2019

Release Note: Added Tentacle support for spaces. Breaking change Deregister commands no longer remove trust for the server.

@TomPeters TomPeters closed this Jan 25, 2019

This comment has been minimized.

Copy link

commented Apr 25, 2019

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.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
1 participant
You can’t perform that action at this time.