cloudx-proxy 0.3.1__tar.gz → 0.3.2__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/CHANGELOG.md +2 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/PKG-INFO +47 -13
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/README.md +46 -12
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy/_version.py +2 -2
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy.egg-info/PKG-INFO +47 -13
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/.github/workflows/release.yml +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/.gitignore +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/.releaserc +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/CONTRIBUTING.md +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/LICENSE +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy/__init__.py +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy/cli.py +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy/core.py +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy/setup.py +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy.egg-info/SOURCES.txt +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy.egg-info/dependency_links.txt +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy.egg-info/entry_points.txt +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy.egg-info/requires.txt +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/cloudx_proxy.egg-info/top_level.txt +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/package.json +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/pyproject.toml +0 -0
- {cloudx_proxy-0.3.1 → cloudx_proxy-0.3.2}/setup.cfg +0 -0
@@ -1,6 +1,6 @@
|
|
1
1
|
Metadata-Version: 2.2
|
2
2
|
Name: cloudx-proxy
|
3
|
-
Version: 0.3.
|
3
|
+
Version: 0.3.2
|
4
4
|
Summary: SSH proxy command to connect VSCode with Cloud9/CloudX instance using AWS Systems Manager
|
5
5
|
Author-email: easytocloud <info@easytocloud.com>
|
6
6
|
License: MIT License
|
@@ -163,28 +163,62 @@ When adding new instances to an existing environment, the setup command will onl
|
|
163
163
|
|
164
164
|
## Usage
|
165
165
|
|
166
|
-
### Command Line
|
166
|
+
### Command Line Options
|
167
167
|
|
168
|
+
#### Setup Command
|
168
169
|
```bash
|
169
|
-
|
170
|
-
|
170
|
+
uvx cloudx-proxy setup [OPTIONS]
|
171
|
+
```
|
172
|
+
|
173
|
+
Options:
|
174
|
+
- `--profile` (default: vscode): AWS profile to use. The profile's IAM user should follow the format cloudX-{env}-{user}. The environment part will be used as the default environment during setup.
|
175
|
+
- `--ssh-key` (default: vscode): Name of the SSH key to create/use. The key will be stored in ~/.ssh/vscode/{name}. This same name can be used in the connect command.
|
176
|
+
- `--aws-env` (optional): AWS environment directory to use. If specified, AWS configuration and credentials will be read from ~/.aws/aws-envs/{env}/.
|
177
|
+
|
178
|
+
Example usage:
|
179
|
+
```bash
|
180
|
+
# Basic setup with defaults
|
181
|
+
uvx cloudx-proxy setup
|
171
182
|
|
172
|
-
#
|
183
|
+
# Setup with custom profile and key
|
184
|
+
uvx cloudx-proxy setup --profile myprofile --ssh-key mykey
|
185
|
+
|
186
|
+
# Setup with AWS environment
|
173
187
|
uvx cloudx-proxy setup --profile myprofile --aws-env prod
|
188
|
+
```
|
174
189
|
|
175
|
-
|
176
|
-
|
190
|
+
#### Connect Command
|
191
|
+
```bash
|
192
|
+
uvx cloudx-proxy connect INSTANCE_ID [PORT] [OPTIONS]
|
193
|
+
```
|
194
|
+
|
195
|
+
Arguments:
|
196
|
+
- `INSTANCE_ID`: The EC2 instance ID to connect to (e.g., i-0123456789abcdef0)
|
197
|
+
- `PORT` (default: 22): The port to forward for SSH connection
|
177
198
|
|
178
|
-
|
179
|
-
|
199
|
+
Options:
|
200
|
+
- `--profile` (default: vscode): AWS profile to use. Should match the profile used in setup.
|
201
|
+
- `--ssh-key` (default: vscode): Name of the SSH key to use. Should match the key name used in setup.
|
202
|
+
- `--region` (optional): AWS region to use. If not specified, uses the region from the AWS profile.
|
203
|
+
- `--aws-env` (optional): AWS environment directory to use. Should match the environment used in setup.
|
180
204
|
|
181
|
-
|
182
|
-
|
205
|
+
Example usage:
|
206
|
+
```bash
|
207
|
+
# Connect using defaults
|
208
|
+
uvx cloudx-proxy connect i-0123456789abcdef0
|
209
|
+
|
210
|
+
# Connect with custom profile and key
|
211
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 22 --profile myprofile --ssh-key mykey
|
212
|
+
|
213
|
+
# Connect with custom port and region
|
214
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 2222 --region us-east-1
|
183
215
|
|
184
|
-
# Connect with
|
185
|
-
uvx cloudx-proxy connect i-0123456789abcdef0 22 --
|
216
|
+
# Connect with AWS environment
|
217
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 22 --profile myprofile --aws-env prod
|
186
218
|
```
|
187
219
|
|
220
|
+
Note: The connect command is typically used through the SSH ProxyCommand configuration set up by the setup command. You rarely need to run it directly unless testing the connection.
|
221
|
+
|
188
222
|
### VSCode
|
189
223
|
|
190
224
|
1. Click the "Remote Explorer" icon in the VSCode sidebar
|
@@ -113,28 +113,62 @@ When adding new instances to an existing environment, the setup command will onl
|
|
113
113
|
|
114
114
|
## Usage
|
115
115
|
|
116
|
-
### Command Line
|
116
|
+
### Command Line Options
|
117
117
|
|
118
|
+
#### Setup Command
|
118
119
|
```bash
|
119
|
-
|
120
|
-
|
120
|
+
uvx cloudx-proxy setup [OPTIONS]
|
121
|
+
```
|
122
|
+
|
123
|
+
Options:
|
124
|
+
- `--profile` (default: vscode): AWS profile to use. The profile's IAM user should follow the format cloudX-{env}-{user}. The environment part will be used as the default environment during setup.
|
125
|
+
- `--ssh-key` (default: vscode): Name of the SSH key to create/use. The key will be stored in ~/.ssh/vscode/{name}. This same name can be used in the connect command.
|
126
|
+
- `--aws-env` (optional): AWS environment directory to use. If specified, AWS configuration and credentials will be read from ~/.aws/aws-envs/{env}/.
|
127
|
+
|
128
|
+
Example usage:
|
129
|
+
```bash
|
130
|
+
# Basic setup with defaults
|
131
|
+
uvx cloudx-proxy setup
|
121
132
|
|
122
|
-
#
|
133
|
+
# Setup with custom profile and key
|
134
|
+
uvx cloudx-proxy setup --profile myprofile --ssh-key mykey
|
135
|
+
|
136
|
+
# Setup with AWS environment
|
123
137
|
uvx cloudx-proxy setup --profile myprofile --aws-env prod
|
138
|
+
```
|
124
139
|
|
125
|
-
|
126
|
-
|
140
|
+
#### Connect Command
|
141
|
+
```bash
|
142
|
+
uvx cloudx-proxy connect INSTANCE_ID [PORT] [OPTIONS]
|
143
|
+
```
|
144
|
+
|
145
|
+
Arguments:
|
146
|
+
- `INSTANCE_ID`: The EC2 instance ID to connect to (e.g., i-0123456789abcdef0)
|
147
|
+
- `PORT` (default: 22): The port to forward for SSH connection
|
127
148
|
|
128
|
-
|
129
|
-
|
149
|
+
Options:
|
150
|
+
- `--profile` (default: vscode): AWS profile to use. Should match the profile used in setup.
|
151
|
+
- `--ssh-key` (default: vscode): Name of the SSH key to use. Should match the key name used in setup.
|
152
|
+
- `--region` (optional): AWS region to use. If not specified, uses the region from the AWS profile.
|
153
|
+
- `--aws-env` (optional): AWS environment directory to use. Should match the environment used in setup.
|
130
154
|
|
131
|
-
|
132
|
-
|
155
|
+
Example usage:
|
156
|
+
```bash
|
157
|
+
# Connect using defaults
|
158
|
+
uvx cloudx-proxy connect i-0123456789abcdef0
|
159
|
+
|
160
|
+
# Connect with custom profile and key
|
161
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 22 --profile myprofile --ssh-key mykey
|
162
|
+
|
163
|
+
# Connect with custom port and region
|
164
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 2222 --region us-east-1
|
133
165
|
|
134
|
-
# Connect with
|
135
|
-
uvx cloudx-proxy connect i-0123456789abcdef0 22 --
|
166
|
+
# Connect with AWS environment
|
167
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 22 --profile myprofile --aws-env prod
|
136
168
|
```
|
137
169
|
|
170
|
+
Note: The connect command is typically used through the SSH ProxyCommand configuration set up by the setup command. You rarely need to run it directly unless testing the connection.
|
171
|
+
|
138
172
|
### VSCode
|
139
173
|
|
140
174
|
1. Click the "Remote Explorer" icon in the VSCode sidebar
|
@@ -1,6 +1,6 @@
|
|
1
1
|
Metadata-Version: 2.2
|
2
2
|
Name: cloudx-proxy
|
3
|
-
Version: 0.3.
|
3
|
+
Version: 0.3.2
|
4
4
|
Summary: SSH proxy command to connect VSCode with Cloud9/CloudX instance using AWS Systems Manager
|
5
5
|
Author-email: easytocloud <info@easytocloud.com>
|
6
6
|
License: MIT License
|
@@ -163,28 +163,62 @@ When adding new instances to an existing environment, the setup command will onl
|
|
163
163
|
|
164
164
|
## Usage
|
165
165
|
|
166
|
-
### Command Line
|
166
|
+
### Command Line Options
|
167
167
|
|
168
|
+
#### Setup Command
|
168
169
|
```bash
|
169
|
-
|
170
|
-
|
170
|
+
uvx cloudx-proxy setup [OPTIONS]
|
171
|
+
```
|
172
|
+
|
173
|
+
Options:
|
174
|
+
- `--profile` (default: vscode): AWS profile to use. The profile's IAM user should follow the format cloudX-{env}-{user}. The environment part will be used as the default environment during setup.
|
175
|
+
- `--ssh-key` (default: vscode): Name of the SSH key to create/use. The key will be stored in ~/.ssh/vscode/{name}. This same name can be used in the connect command.
|
176
|
+
- `--aws-env` (optional): AWS environment directory to use. If specified, AWS configuration and credentials will be read from ~/.aws/aws-envs/{env}/.
|
177
|
+
|
178
|
+
Example usage:
|
179
|
+
```bash
|
180
|
+
# Basic setup with defaults
|
181
|
+
uvx cloudx-proxy setup
|
171
182
|
|
172
|
-
#
|
183
|
+
# Setup with custom profile and key
|
184
|
+
uvx cloudx-proxy setup --profile myprofile --ssh-key mykey
|
185
|
+
|
186
|
+
# Setup with AWS environment
|
173
187
|
uvx cloudx-proxy setup --profile myprofile --aws-env prod
|
188
|
+
```
|
174
189
|
|
175
|
-
|
176
|
-
|
190
|
+
#### Connect Command
|
191
|
+
```bash
|
192
|
+
uvx cloudx-proxy connect INSTANCE_ID [PORT] [OPTIONS]
|
193
|
+
```
|
194
|
+
|
195
|
+
Arguments:
|
196
|
+
- `INSTANCE_ID`: The EC2 instance ID to connect to (e.g., i-0123456789abcdef0)
|
197
|
+
- `PORT` (default: 22): The port to forward for SSH connection
|
177
198
|
|
178
|
-
|
179
|
-
|
199
|
+
Options:
|
200
|
+
- `--profile` (default: vscode): AWS profile to use. Should match the profile used in setup.
|
201
|
+
- `--ssh-key` (default: vscode): Name of the SSH key to use. Should match the key name used in setup.
|
202
|
+
- `--region` (optional): AWS region to use. If not specified, uses the region from the AWS profile.
|
203
|
+
- `--aws-env` (optional): AWS environment directory to use. Should match the environment used in setup.
|
180
204
|
|
181
|
-
|
182
|
-
|
205
|
+
Example usage:
|
206
|
+
```bash
|
207
|
+
# Connect using defaults
|
208
|
+
uvx cloudx-proxy connect i-0123456789abcdef0
|
209
|
+
|
210
|
+
# Connect with custom profile and key
|
211
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 22 --profile myprofile --ssh-key mykey
|
212
|
+
|
213
|
+
# Connect with custom port and region
|
214
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 2222 --region us-east-1
|
183
215
|
|
184
|
-
# Connect with
|
185
|
-
uvx cloudx-proxy connect i-0123456789abcdef0 22 --
|
216
|
+
# Connect with AWS environment
|
217
|
+
uvx cloudx-proxy connect i-0123456789abcdef0 22 --profile myprofile --aws-env prod
|
186
218
|
```
|
187
219
|
|
220
|
+
Note: The connect command is typically used through the SSH ProxyCommand configuration set up by the setup command. You rarely need to run it directly unless testing the connection.
|
221
|
+
|
188
222
|
### VSCode
|
189
223
|
|
190
224
|
1. Click the "Remote Explorer" icon in the VSCode sidebar
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|
File without changes
|