Open instance ports from the CLI - #442
Draft
callen-bot wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
brev ports open <instance-or-node> <port>withaddas an alias--allow <CIDR>source restrictionsWhy
PR #441 exposes existing port mappings in the CLI, but users still have to switch to the console to open one. This stacked follow-up mirrors the console raw-port flow for managed instances and registered compute nodes.
Impact
Users can expose a destination port without leaving the terminal, choose the protocol, restrict inbound sources, and consume the allocated public mapping in scripts.
Stack
Validation
go test -race ./pkg/cmd/ports ./pkg/cmd/util ./pkg/cmdmake fmtcheckmake fast-buildmake vetmake lint