Repository navigation
Custom variables in settings.json for easier profile configuration #9185
Description
Description of the new feature/enhancement
Let one define custom variables in settings.json for use with profiles.
E.g. define myCustomVariable for later use within commandline to avoid adding same long path to SSH key file for every profile name.
Would also be great to reuse current profile parameters such as "name" to connect to this hostname by stating $profile.name with SSH as shown in example.
Proposed technical implementation details (optional)
"profiles":
{
"defaults":
{
"myCustomVariable": "C:\\Users\\USERNAME\\SSH_KEY_FILE_PATH.key"
},
"list":
[
{
"name": "HOSTNAME",
"commandline": "ssh -i $myCustomVariable $profile.name",
},
Activity
zadjii-msft commentedon Feb 26, 2021
This isn't a terrible idea, but I'm guessing that this would not play well with the Settings UI. So this would end up being a feature that would work well if you exclusively used the json settings. I'm gonna stick this in the freezer for now. It's a reasonable request, but not one we're likely to get to anytime soon.
DHowett commentedon Jan 14, 2025
You may not be able to achieve exactly this today, but... it seems much better-served by:
ssh_config(to specify the username; configure it once per person and let it be)This at least prevents you from having to override everyone's settings every time you provision a new server. Plus,
ssh_configsupports wildcards:(as an aside: why are you launching PowerShell just to launch
ssh? You can launchsshdirectly.)DHowett commentedon Jan 18, 2025
Oh! I get it.
I think
SSHADMINwill work as expected if you use the Windows shell syntax for environment variables:%SSHADMIN%.(
$env:is of course PowerShell specific;%works everywhere else on Windows.)