2013-09-03 22:45:49 +00:00
# Cobra
A Commander for modern go CLI interactions
2015-04-09 23:15:21 +00:00
[![Build Status ](https://travis-ci.org/spf13/cobra.svg )](https://travis-ci.org/spf13/cobra)
2013-09-24 21:08:47 +00:00
2013-09-03 22:45:49 +00:00
## Overview
2013-11-05 17:40:10 +00:00
Cobra is a commander providing a simple interface to create powerful modern CLI
2014-09-08 14:18:24 +00:00
interfaces similar to git & go tools. In addition to providing an interface, Cobra
2013-11-05 17:40:10 +00:00
simultaneously provides a controller to organize your application code.
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
Inspired by go, go-Commander, gh and subcommand, Cobra improves on these by
providing **fully posix compliant flags** (including short & long versions),
**nesting commands**, and the ability to **define your own help and usage** for any or
all commands.
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
Cobra has an exceptionally clean interface and simple design without needless
constructors or initialization methods.
2013-09-03 22:45:49 +00:00
2014-06-17 16:32:27 +00:00
Applications built with Cobra commands are designed to be as user friendly as
possible. Flags can be placed before or after the command (as long as a
confusing space isn’ t provided). Both short and long flags can be used. A
command need not even be fully typed. The shortest unambiguous string will
suffice. Help is automatically generated and available for the application or
for a specific command using either the help command or the --help flag.
2013-11-05 17:40:10 +00:00
## Concepts
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
Cobra is built on a structure of commands & flags.
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
**Commands** represent actions and **Flags** are modifiers for those actions.
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
In the following example 'server' is a command and 'port' is a flag.
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
hugo server --port=1313
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
### Commands
2013-09-03 22:45:49 +00:00
Command is the central point of the application. Each interaction that
the application supports will be contained in a Command. A command can
have children commands and optionally run an action.
In the example above 'server' is the command
2013-11-05 17:40:10 +00:00
A Command has the following structure:
type Command struct {
Use string // The one-line usage message.
Short string // The short description shown in the 'help' output.
Long string // The long message shown in the 'help < this-command > ' output.
Run func(cmd *Command, args []string) // Run runs the command.
}
2013-09-03 22:45:49 +00:00
### Flags
2013-11-05 17:40:10 +00:00
A Flag is a way to modify the behavior of an command. Cobra supports
fully posix compliant flags as well as the go flag package.
2014-01-12 05:34:06 +00:00
A Cobra command can define flags that persist through to children commands
2013-11-05 17:40:10 +00:00
and flags that are only available to that command.
2013-09-03 22:45:49 +00:00
In the example above 'port' is the flag.
2013-11-05 17:40:10 +00:00
Flag functionality is provided by the [pflag
libary](https://github.com/ogier/pflag), a fork of the flag standard library
which maintains the same interface while adding posix compliance.
2013-09-03 22:45:49 +00:00
## Usage
2013-11-05 17:40:10 +00:00
Cobra works by creating a set of commands and then organizing them into a tree.
The tree defines the structure of the application.
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
Once each command is defined with it's corresponding flags, then the
tree is assigned to the commander which is finally executed.
### Installing
2013-09-03 22:45:49 +00:00
Using Cobra is easy. First use go get to install the latest version
of the library.
$ go get github.com/spf13/cobra
Next include cobra in your application.
import "github.com/spf13/cobra"
2013-11-05 17:40:10 +00:00
### Create the root command
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
The root command represents your binary itself.
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
Cobra doesn't require any special constructors. Simply create your commands.
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
var HugoCmd = & cobra.Command{
Use: "hugo",
Short: "Hugo is a very fast static site generator",
Long: `A Fast and Flexible Static Site Generator built with
love by spf13 and friends in Go.
Complete documentation is available at http://hugo.spf13.com`,
Run: func(cmd *cobra.Command, args []string) {
// Do Stuff Here
},
}
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
### Create additional commands
2013-09-24 20:52:33 +00:00
2013-11-05 17:40:10 +00:00
Additional commands can be defined.
var versionCmd = & cobra.Command{
Use: "version",
Short: "Print the version number of Hugo",
Long: `All software has versions. This is Hugo's` ,
Run: func(cmd *cobra.Command, args []string) {
fmt.Println("Hugo Static Site Generator v0.9 -- HEAD")
},
}
2014-05-27 18:52:47 +00:00
### Attach command to its parent
2013-11-05 17:40:10 +00:00
In this example we are attaching it to the root, but commands can be attached at any level.
HugoCmd.AddCommand(versionCmd)
### Assign flags to a command
2014-12-19 03:41:49 +00:00
Since the flags are defined and used in different locations, we need to
define a variable outside with the correct scope to assign the flag to
work with.
2013-11-05 17:40:10 +00:00
var Verbose bool
var Source string
There are two different approaches to assign a flag.
#### Persistent Flags
A flag can be 'persistent' meaning that this flag will be available to the
command it's assigned to as well as every command under that command. For
global flags assign a flag as a persistent flag on the root.
HugoCmd.PersistentFlags().BoolVarP(& Verbose, "verbose", "v", false, "verbose output")
#### Local Flags
A flag can also be assigned locally which will only apply to that specific command.
HugoCmd.Flags().StringVarP(& Source, "source", "s", "", "Source directory to read from")
2015-03-13 03:40:00 +00:00
### Remove a command from its parent
2015-04-16 21:15:33 +00:00
Removing a command is not a common action in simple programs but it allows 3rd parties to customize an existing command tree.
2015-03-13 03:40:00 +00:00
2015-04-26 12:53:29 +00:00
In this example, we remove the existing `VersionCmd` command of an existing root command, and we replace it by our own version.
2015-03-13 03:40:00 +00:00
mainlib.RootCmd.RemoveCommand(mainlib.VersionCmd)
mainlib.RootCmd.AddCommand(versionCmd)
2013-11-05 17:40:10 +00:00
### Once all commands and flags are defined, Execute the commands
Execute should be run on the root for clarity, though it can be called on any command.
HugoCmd.Execute()
2013-09-24 20:52:33 +00:00
## Example
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
In the example below we have defined three commands. Two are at the top level
and one (cmdTimes) is a child of one of the top commands. In this case the root
2014-08-06 00:28:49 +00:00
is not executable meaning that a subcommand is required. This is accomplished
2013-11-05 17:40:10 +00:00
by not providing a 'Run' for the 'rootCmd'.
We have only defined one flag for a single command.
More documentation about flags is available at https://github.com/spf13/pflag
2013-12-21 10:32:14 +00:00
import(
2013-09-03 22:45:49 +00:00
"github.com/spf13/cobra"
"fmt"
"strings"
)
func main() {
var echoTimes int
var cmdPrint = & cobra.Command{
Use: "print [string to print]",
Short: "Print anything to the screen",
2013-09-24 20:45:20 +00:00
Long: `print is for printing anything back to the screen.
For many years people have printed back to the screen.
`,
2013-09-03 22:45:49 +00:00
Run: func(cmd *cobra.Command, args []string) {
fmt.Println("Print: " + strings.Join(args, " "))
},
}
2013-09-24 20:52:33 +00:00
var cmdEcho = & cobra.Command{
2013-09-03 22:45:49 +00:00
Use: "echo [string to echo]",
Short: "Echo anything to the screen",
2013-09-24 20:45:20 +00:00
Long: `echo is for echoing anything back.
Echo works a lot like print, except it has a child command.
`,
Run: func(cmd *cobra.Command, args []string) {
fmt.Println("Print: " + strings.Join(args, " "))
},
}
2013-09-24 20:52:33 +00:00
var cmdTimes = & cobra.Command{
2013-09-24 20:45:20 +00:00
Use: "times [# times] [string to echo]",
Short: "Echo anything to the screen more times",
Long: `echo things multiple times back to the user by providing
a count and a string.`,
2013-09-03 22:45:49 +00:00
Run: func(cmd *cobra.Command, args []string) {
for i:=0; i < echoTimes ; i + + {
fmt.Println("Echo: " + strings.Join(args, " "))
}
},
}
2013-12-21 10:32:14 +00:00
cmdTimes.Flags().IntVarP(& echoTimes, "times", "t", 1, "times to echo the input")
2013-09-03 22:45:49 +00:00
2013-11-05 17:40:10 +00:00
var rootCmd = & cobra.Command{Use: "app"}
rootCmd.AddCommand(cmdPrint, cmdEcho)
2013-09-24 20:45:20 +00:00
cmdEcho.AddCommand(cmdTimes)
2013-11-05 17:40:10 +00:00
rootCmd.Execute()
}
For a more complete example of a larger application, please checkout [Hugo ](http://hugo.spf13.com )
## The Help Command
2015-02-02 19:53:21 +00:00
Cobra automatically adds a help command to your application when you have subcommands.
2013-11-05 17:40:10 +00:00
This will be called when a user runs 'app help'. Additionally help will also
support all other commands as input. Say for instance you have a command called
'create' without any additional configuration cobra will work when 'app help
2015-02-02 19:53:21 +00:00
create' is called. Every command will automatically have the '--help' flag added.
2013-11-05 17:40:10 +00:00
### Example
The following output is automatically generated by cobra. Nothing beyond the
command and flag definitions are needed.
> hugo help
A Fast and Flexible Static Site Generator built with
love by spf13 and friends in Go.
Complete documentation is available at http://hugo.spf13.com
Usage:
hugo [flags]
hugo [command]
Available Commands:
server :: Hugo runs it's own a webserver to render the files
version :: Print the version number of Hugo
check :: Check content in the source directory
benchmark :: Benchmark hugo by building a site a number of times
help [command] :: Help about any command
Available Flags:
-b, --base-url="": hostname (and path) to the root eg. http://spf13.com/
-D, --build-drafts=false: include content marked as draft
--config="": config file (default is path/config.yaml|json|toml)
-d, --destination="": filesystem path to write files to
-s, --source="": filesystem path to read files relative from
--stepAnalysis=false: display memory and timing of different steps of the program
--uglyurls=false: if true, use /filename.html instead of /filename/
-v, --verbose=false: verbose output
-w, --watch=false: watch filesystem for changes and recreate as needed
Use "hugo help [command]" for more information about that command.
Help is just a command like any other. There is no special logic or behavior
around it. In fact you can provide your own if you want.
### Defining your own help
You can provide your own Help command or you own template for the default command to use.
The default help command is
func (c *Command) initHelp() {
if c.helpCommand == nil {
c.helpCommand = & Command{
Use: "help [command]",
Short: "Help about any command",
Long: `Help provides help for any command in the application.
Simply type ` + c.Name() + ` help [path to command] for full details.`,
Run: c.HelpFunc(),
}
}
c.AddCommand(c.helpCommand)
2013-09-03 22:45:49 +00:00
}
2013-11-05 17:40:10 +00:00
You can provide your own command, function or template through the following methods.
command.SetHelpCommand(cmd *Command)
command.SetHelpFunc(f func(*Command, []string))
command.SetHelpTemplate(s string)
The latter two will also apply to any children commands.
## Usage
When the user provides an invalid flag or invalid command Cobra responds by
showing the user the 'usage'
### Example
2014-06-17 16:32:27 +00:00
You may recognize this from the help above. That's because the default help
2013-11-05 17:40:10 +00:00
embeds the usage as part of it's output.
Usage:
hugo [flags]
hugo [command]
Available Commands:
2014-06-17 16:28:42 +00:00
server Hugo runs it's own a webserver to render the files
version Print the version number of Hugo
check Check content in the source directory
benchmark Benchmark hugo by building a site a number of times
help [command] Help about any command
2013-11-05 17:40:10 +00:00
Available Flags:
-b, --base-url="": hostname (and path) to the root eg. http://spf13.com/
-D, --build-drafts=false: include content marked as draft
--config="": config file (default is path/config.yaml|json|toml)
-d, --destination="": filesystem path to write files to
-s, --source="": filesystem path to read files relative from
--stepAnalysis=false: display memory and timing of different steps of the program
--uglyurls=false: if true, use /filename.html instead of /filename/
-v, --verbose=false: verbose output
-w, --watch=false: watch filesystem for changes and recreate as needed
### Defining your own usage
You can provide your own usage function or template for cobra to use.
The default usage function is
return func(c *Command) error {
err := tmpl(c.Out(), c.UsageTemplate(), c)
return err
}
Like help the function and template are over ridable through public methods.
command.SetUsageFunc(f func(*Command) error)
command.SetUsageTemplate(s string)
Auto generation of markdown docs!
An example from the kubernetes project, for the `kubectl config`
command, which as subcommands, and flags, and all sorts of stuff, it
will generate markdown like so:
config modifies .kubeconfig files
config modifies .kubeconfig files using subcommands like "kubectl config set current-context my-context"
```
kubectl config SUBCOMMAND
```
```
--envvar=false: use the .kubeconfig from $KUBECONFIG
--global=false: use the .kubeconfig from /home/username
-h, --help=false: help for config
--kubeconfig="": use a particular .kubeconfig file
--local=false: use the .kubeconfig in the current directory
```
```
--alsologtostderr=false: log to standard error as well as files
--api-version="": The API version to use when talking to the server
-a, --auth-path="": Path to the auth info file. If missing, prompt the user. Only used if using https.
--certificate-authority="": Path to a cert. file for the certificate authority.
--client-certificate="": Path to a client key file for TLS.
--client-key="": Path to a client key file for TLS.
--cluster="": The name of the kubeconfig cluster to use
--context="": The name of the kubeconfig context to use
--insecure-skip-tls-verify=false: If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.
--log_backtrace_at=:0: when logging hits line file:N, emit a stack trace
--log_dir=: If non-empty, write log files in this directory
--log_flush_frequency=5s: Maximum number of seconds between log flushes
--logtostderr=true: log to standard error instead of files
--match-server-version=false: Require server version to match client version
--namespace="": If present, the namespace scope for this CLI request.
--password="": Password for basic authentication to the API server.
-s, --server="": The address and port of the Kubernetes API server
--stderrthreshold=2: logs at or above this threshold go to stderr
--token="": Bearer token for authentication to the API server.
--user="": The name of the kubeconfig user to use
--username="": Username for basic authentication to the API server.
--v=0: log level for V logs
--validate=false: If true, use a schema to validate the input before sending it
--vmodule=: comma-separated list of pattern=N settings for file-filtered logging
```
* [kubectl](kubectl.md) - kubectl controls the Kubernetes cluster manager
* [kubectl config set](kubectl_config_set.md) - Sets an individual value in a .kubeconfig file
* [kubectl config set-cluster](kubectl_config_set-cluster.md) - Sets a cluster entry in .kubeconfig
* [kubectl config set-context](kubectl_config_set-context.md) - Sets a context entry in .kubeconfig
* [kubectl config set-credentials](kubectl_config_set-credentials.md) - Sets a user entry in .kubeconfig
* [kubectl config unset](kubectl_config_unset.md) - Unsets an individual value in a .kubeconfig file
* [kubectl config use-context](kubectl_config_use-context.md) - Sets the current-context in a .kubeconfig file
* [kubectl config view](kubectl_config_view.md) - displays merged .kubeconfig settings or a specified .kubeconfig file.
2015-04-07 03:38:51 +00:00
## Generating markdown formatted documentation for your command
Cobra can generate a markdown formatted document based on the subcommands, flags, etc. A simple example of how to do this for your command can be found in [Markdown Docs ](md_docs.md )
2015-03-16 19:31:03 +00:00
## Generating bash completions for your command
Cobra can generate a bash completions file. If you add more information to your command these completions can be amazingly powerful and flexible. Read more about [Bash Completions ](bash_completions.md )
2013-11-05 17:40:10 +00:00
2014-06-17 16:32:27 +00:00
## Debugging
Cobra provides a ‘ DebugFlags’ method on a command which when called will print
out everything Cobra knows about the flags for each command
### Example
command.DebugFlags()
2013-09-03 22:45:49 +00:00
## Release Notes
2014-06-17 16:32:27 +00:00
* **0.9.0** June 17, 2014
* flags can appears anywhere in the args (provided they are unambiguous)
* --help prints usage screen for app or command
* Prefix matching for commands
* Cleaner looking help and usage output
* Extensive test suite
2013-11-05 17:40:10 +00:00
* **0.8.0** Nov 5, 2013
* Reworked interface to remove commander completely
* Command now primary structure
* No initialization needed
* Usage & Help templates & functions definable at any level
* Updated Readme
2013-09-24 20:45:20 +00:00
* **0.7.0** Sept 24, 2013
* Needs more eyes
* Test suite
* Support for automatic error messages
* Support for help command
* Support for printing to any io.Writer instead of os.Stderr
* Support for persistent flags which cascade down tree
* Ready for integration into Hugo
2013-09-03 22:45:49 +00:00
* **0.1.0** Sept 3, 2013
* Implement first draft
2013-09-24 20:45:20 +00:00
## ToDo
* Launch proper documentation site
2013-09-03 22:45:49 +00:00
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
## Contributors
Names in no particular order:
* [spf13 ](https://github.com/spf13 )
## License
2014-05-05 00:01:50 +00:00
Cobra is released under the Apache 2.0 license. See [LICENSE.txt ](https://github.com/spf13/cobra/blob/master/LICENSE.txt )
2014-01-02 17:58:43 +00:00
[![Bitdeli Badge ](https://d2weczhvl823v0.cloudfront.net/spf13/cobra/trend.png )](https://bitdeli.com/free "Bitdeli Badge")