From 6509eb51ec74c4711e17ea9cf0de7a25fe353acc Mon Sep 17 00:00:00 2001 From: Anmol Sethi Date: Fri, 16 Dec 2022 00:40:51 -0800 Subject: [PATCH] ci/aws: Format docs better --- ci/release/aws/ensure.sh | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/ci/release/aws/ensure.sh b/ci/release/aws/ensure.sh index 6452ec7e1..c850e4315 100755 --- a/ci/release/aws/ensure.sh +++ b/ci/release/aws/ensure.sh @@ -462,15 +462,25 @@ EOF # Use the following to run a command in a pure MSYS2 shell: # ssh "$CI_D2_WINDOWS_AMD64" 'C:\msys64\msys2_shell.cmd -defterm -here -no-start -mingw64 -c "echo hi"' -# In case msys2 improves in the future and allows for noninteractive commands via ssh "$CI_D2_WINDOWS_AMD64" echo hi -# The following will set the OpenSSH shell to MSYS2 instead of PowerShell. -# But PowerShell as the default is better anyway as it gives us access to both the UNIX userspace and Windows tools like wix/dotnet/winget. +# In case MSYS2 improves in the future and allows for noninteractive commands the +# following will set the OpenSSH shell to MSYS2 instead of PowerShell. +# +# Right now, setting MSYS2 to the DefaultShell like this will make it start bash in +# interactive mode always. Even for ssh "$CI_D2_WINDOWS_AMD64" echo hi. And so you'll end +# up with a blank prompt on which to input commands instead of having it execute the +# command you passed in via ssh. +# +# PowerShell as the default is better anyway as it gives us access to both the UNIX +# userspace and Windows tools like wix/dotnet/winget. +# +# To set: # < utf8: https://stackoverflow.com/a/34969243/4283659 # \$null = New-Item -Force C:\msys64\sshd_default_shell.cmd -Value (Get-Content -Path C:\msys64\sshd_default_shell.cmd | Out-String) # Set-ItemProperty -Path HKLM:\SOFTWARE\OpenSSH -Name DefaultShell -Value C:\msys64\sshd_default_shell.cmd # EOF +# # To undo: # <