-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Gitpod port control via gp-cli #9286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yes please! |
Removing from project as associated to epic: #9262 |
Some updates here...
Please see: #10388 (documentation pending) However I'm not sure what you mean by "if local-companion" is available, in this context?
This is also described in: #9930 (not yet implemented) |
@loujaybee can you please also add a possibility to fetch the port status as JSON result. The printed cli table is nice in the terminal, but hard to use in bash,... scripts (see #10388 implementation) for example with the --json argument |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
for me the current gp foreward-port is missleading it should be changed because it control the public mode
Please introduce a clear API for the port management via the gp cli with the following functions:
in the following text [local] means always a port that is accessibly from the local computer via local-companion / vscode / ...
gp port 8080 --public
orgp port 8080 --private
gp port status
-> returns all ports with the current status and if local-companion is availablegp port -R 80:127.0.0.1:3000
gp port -L 80:127.0.0.1:3000
. ... use SSH logic because this is well knowngp port -KR 80
gp port -KL 80
... again use SSH logic for deleting remote and local port forwardsThis would allow having full control of the workspace.
The text was updated successfully, but these errors were encountered: