Skip to content

Commit 1742499

Browse files
authored
remove S3 references in connections docs (#2884)
1 parent d42709e commit 1742499

1 file changed

Lines changed: 2 additions & 10 deletions

File tree

docs/docs/connections.mdx

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ import { VersionBadge } from "@site/src/components/versionbadge";
88

99
# Connections
1010

11-
Wave allows users to connect to various machines and unify them together in a way that preserves the unique behavior of each. At the moment, this extends to SSH remote connections, local WSL connections, and AWS S3 buckets.
11+
Wave allows users to connect to various machines and unify them together in a way that preserves the unique behavior of each. At the moment, this extends to SSH remote connections and local WSL connections.
1212

1313
## Access a Connection in a Block
1414

@@ -24,19 +24,13 @@ For WSL Connections:
2424

2525
- `wsl://<distribution name>`
2626

27-
For AWS S3 Connections:
28-
29-
- `aws:[profile]`
30-
3127
Alternatively, if the connection already exists in the dropdown list, you can either click it or navigate to it with arrow keys and press enter to connect.
3228

3329
![a dropdown showing a list of connections that already exist](./img/connection-dropdown.png)
3430

3531
## Different Types of Connections
3632

37-
As there are several different types of connections, not all of the types have access to the same features. For instance, AWS S3 connections can only be used in preview widgets (directory, image viewer, code editor, etc.). Meanwhile, SSH and WSL connections can always work in terminal widgets, and if `wsh` shell extensions are installed, they can also work in preview widgets and the sysinfo widget.
38-
39-
As such, certain features will not be available for certain types of connections. As an example, AWS S3 connections cannot run startup scripts as they are not capable of running scripts.
33+
As there are several different types of connections, not all of the types have access to the same features. SSH and WSL connections can always work in terminal widgets, and if `wsh` shell extensions are installed, they can also work in preview widgets and the sysinfo widget.
4034

4135
## What are wsh Shell Extensions?
4236

@@ -90,8 +84,6 @@ The SSH values that are loaded into the dropdown by default are obtained by pars
9084

9185
WSL connections are added by searching the installed WSL distributions as they appear in the Windows Registry. They also exist in the `config/connections.json` file similarly to SSH connections.
9286

93-
AWS S3 Connections are added by parsing the `~/.aws/config` file. Unlike the SSH and WSL connections, these are not stored in the `config/connections.json` file.
94-
9587
## SSH Config Parsing
9688

9789
At the moment, we are capable of parsing any SSH config file that does not contain the `Match` keyword. This keyword is incompatible with a library we are using, but we are hoping to fix that soon. While all other valid keywords are parsed, we only support the functionality of a small subset of them at the moment:

0 commit comments

Comments
 (0)