Skip to content
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.

Sign up for GitHub

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

Fix the connect command usage info #819

Merged
merged 1 commit into from
Sep 30, 2022
Merged

Fix the connect command usage info #819

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/4-user-guide/1-the-zarf-cli/100-cli-commands/zarf_connect.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Packages can provide service manifests that define their own shortcut connection
Even if the packages you deploy don't define their own shortcut connection options, you can use the command flags to connect into specific resources. You can read the command flag descriptions below to get a better idea how to connect to whatever resource you are trying to connect to.

```
zarf connect <REGISTRY|LOGGING|GIT> [flags]
zarf connect {REGISTRY|LOGGING|GIT|connect-name} [flags]
```

### Options
Expand Down
2 changes: 1 addition & 1 deletion src/cmd/connect.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ var (
cliOnly bool

connectCmd = &cobra.Command{
Use: "connect <REGISTRY|LOGGING|GIT>",
Use: "connect {REGISTRY|LOGGING|GIT|connect-name}",
Aliases: []string{"c"},
Short: "Access services or pods deployed in the cluster.",
Long: "Uses a k8s port-forward to connect to resources within the cluster referenced by your kube-context.\n" +
Expand Down