Fix the connect command usage info (#819)

zarf-dev · Sep 30, 2022 · ba6e8dc · ba6e8dc
1 parent 2df1298
commit ba6e8dc
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/4-user-guide/1-the-zarf-cli/100-cli-commands/zarf_connect.md b/docs/4-user-guide/1-the-zarf-cli/100-cli-commands/zarf_connect.md
@@ -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

diff --git a/src/cmd/connect.go b/src/cmd/connect.go
@@ -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" +