It will be used later by the Coder Settings view to allow usersto enable or disable SSH hostname wildcard configuration.

Updated the UI component to allow configuration by the user

when generating the ssh config for Coder Gateway.Up until now we just checked if the Coder deployment supportsthis feature, but now users have to option to continue touse expanded hostnames in the ssh config.

CLIManager can be created with default settings (simplifies testing),among which the ssh wildcard config is enabled. But in reality theconfig can be disabled by the user.

…rd config was changedCurrently, if a user starts a connection with wildcard enabled and then later on it disablesthe wildcard config then the recent connections becomes unusable because the hostnames are invalid.The issue can reproduce the other way around as well (start with wildcard ssh config disabled,start an IDE and then later on enable wildcard config)This commit addresses the issue by resolving the hostname on demand when the user wants toopen the remote IDE from the recent connections panel.

Connections started with two different hostnames (because of the ssh wildcard config)can be rendered twice in the Recent projects panel.With this commit we ignore the hostname and instead use the workspace name and deployment URL.

code-asher left a comment