[ISSUE] Supervisor not completely honor --listen-ctl or HAB_LISTEN_CTL

[sam1el]

When setting --listen-ctl or HAB_LISTEN_CTL on a system. The supervisor will use it however, any subsequent commands to the supervisor including hab svc load my/service
This behavior happens wether it is set in the supervisor, the system env or directly in the command line.

We also looked at the API for Census and Butterfly and the port setting is not persisted there no matter where it is set either.
We tested on Red Hat Linux 6, 7, 8 Windows 2008r2, 2012r2, 2016 and 2019

For ease of use it would make sense for the supervisor to take the port change as it new default rather than having to type hab svc load my/service -r 127.0.0.1:19632 with every new command to the supervisor. It seems counter-intuitive to have to add extra arguments to existing automation or cookbooks to account for something the supervisor you would think the supervisor to know already

Aha! Link: https://chef.aha.io/features/APPDL-24

[christophermaier]

Just for clarification, this is only for interacting with a Supervisor running on the same machine, but where that Supervisor has been configured for a non-standard control gateway port, correct?

Given that the CLI looks for /hab/sup/default/CTL_SECRET locally to get the shared secret, it makes sense that it should have a corresponding way to access the port, as well.

[sam1el]

yes that is correct

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.