Filepath for download in output incorrect on Remote machines

[zb3qk]

Describe the bug

When using the Remote SSH extension for VSCode in tandem with AWS Toolkit the file path outputted in the Output console when downloading a file from S3 does not match the actual path of the downloaded file. The file path outputted points to a file on the local machine when it instead should point to the file on the remote machine.

To Reproduce

Steps to reproduce the behavior:

1. SSH onto a remote machine using the Remote SSH extension
2. Download a file from S3
3. Command click on the file path written in the AWS Toolkit Output window
4. File cannot be found

Expected behavior

The file path written in the output console should point to the file saved in the remote machine, not a file that does not exist on the local machine.

Screenshots Copied from Console Downloading 0029a9b9-6dd1-49eb-81f9-3b15174681b2... Successfully downloaded file file:///tmp/0029a9b9-6dd1-49eb-81f9-3b15174681b2

Desktop (please complete the following information):

• OS: Linux x64 5.4.134-73.228.amzn2int.x86_64
• Visual Studio Code Extension Host Version: 1.60.0
• AWS Toolkit Version: 1.29.0

[bryceitoc9]

A couple questions:

• What OS is the desktop, and what OS is the remote machine?
• If you ls that file in the remote machine's terminal, does it show up? I wonder if this is a VS Code issue, where it's attempting to open the file locally rather than remote.

[JadenSimon]

By default, links with the scheme file: will point to the local file system. This behavior appears to be intended by VS Code. So the toolkit should instead register a link provider for the output channel to correctly resolve the links to wherever the extension is running.