Missing proxy options to connect Octopus Deploy Status Widget running in Azure DevOps Services to on-prem Octopus #331
Description
For various reasons (including limiting user access to Octopus), we wish to use the Octopus Deploy Status Widget on a (cloud-hosted) Azure DevOps dashboard to monitor pipeline runs in Octopus.
The Octopus instance in question is a locally hosted instance, and the service connections set up for use don't seem to be able to resolve the hostname (Octopus Deploy Status Widget stuck "Loading...", and I've done other tests to show this is a DNS issue), as the domain name is only known within the local network.
We could give the locally hosted Octopus instance a public domain name, but we're trying to avoid this for security reasons. Is there a possibility of adding proxy connection options to the Octopus service connections in ADO to permit traffic to be routed in a way that allows the current hostname to be used?