Add Support for Polling 443 on a different address to the Windows Tentacle Manager

[FinnianDempsey]

Team

• I've assigned a team label to this issue

What happened?

Currently the Tentacle installers don't support the new feature Polling Tentacles over Standard Ports: https://octopus.com/docs/infrastructure/deployment-targets/tentacle/polling-tentacles-over-port-443

The windows installer and linux configuration.sh both create scripts that use --server-comms-port "10943" without allowing for --server-comms-address to be specified.

The linux work is split out to: #793

Reproduction

Use the Windows Installer or Linux configure-tentacle.sh to configure a Polling Tentacle and see --server-comms-port used in the generated scripts

Error and Stacktrace

N/A

More Information

Slack - Internal

Workaround

Copy the generated installer scripts and modify the register-with (or register-worker) command to use --server-comms-address instead of --server-comms-port

E.g. https://octopus.com/docs/infrastructure/deployment-targets/tentacle/polling-tentacles-over-port-443#registering-a-new-tentacle

.\Tentacle register-with --instance MyInstance --server "https://<yoururl>.octopus.app" --server-comms-address "https://polling.<yoururl>.octopus.app" --comms-style TentacleActive --apiKey "API-YOURKEY" --environment "Test" --role "Web"

Feel free to reach out to [email protected] with any questions!