package command import ( "fmt" "io" "os" "strings" "github.com/hashicorp/vault/helper/kv-builder" ) // WriteCommand is a Command that puts data into the Vault. type WriteCommand struct { Meta // The fields below can be overwritten for tests testStdin io.Reader } func (c *WriteCommand) Run(args []string) int { var format string flags := c.Meta.FlagSet("write", FlagSetDefault) flags.StringVar(&format, "format", "table", "") flags.Usage = func() { c.Ui.Error(c.Help()) } if err := flags.Parse(args); err != nil { return 1 } args = flags.Args() if len(args) < 2 { c.Ui.Error("write expects at least two arguments") flags.Usage() return 1 } path := args[0] if path[0] == '/' { path = path[1:] } data, err := c.parseData(args[1:]) if err != nil { c.Ui.Error(fmt.Sprintf( "Error loading data: %s", err)) return 1 } client, err := c.Client() if err != nil { c.Ui.Error(fmt.Sprintf( "Error initializing client: %s", err)) return 2 } secret, err := client.Logical().Write(path, data) if err != nil { c.Ui.Error(fmt.Sprintf( "Error writing data to %s: %s", path, err)) return 1 } if secret == nil { c.Ui.Output(fmt.Sprintf("Success! Data written to: %s", path)) return 0 } return OutputSecret(c.Ui, format, secret) } func (c *WriteCommand) parseData(args []string) (map[string]interface{}, error) { var stdin io.Reader = os.Stdin if c.testStdin != nil { stdin = c.testStdin } builder := &kvbuilder.Builder{Stdin: stdin} if err := builder.Add(args...); err != nil { return nil, err } return builder.Map(), nil } func (c *WriteCommand) Synopsis() string { return "Write secrets or configuration into Vault" } func (c *WriteCommand) Help() string { helpText := ` Usage: vault write [options] path [data] Write data (secrets or configuration) into Vault. Write sends data into Vault at the given path. The behavior of the write is determined by the backend at the given path. For example, writing to "aws/policy/ops" will create an "ops" IAM policy for the AWS backend (configuration), but writing to "consul/foo" will write a value directly into Consul at that key. Check the documentation of the logical backend you're using for more information on key structure. Data is sent via additional arguments in "key=value" pairs. If value begins with an "@", then it is loaded from a file. If you want to start the value with a literal "@", then prefix the "@" with a slash: "\@". General Options: -address=TODO The address of the Vault server. -ca-cert=path Path to a PEM encoded CA cert file to use to verify the Vault server SSL certificate. -ca-path=path Path to a directory of PEM encoded CA cert files to verify the Vault server SSL certificate. If both -ca-cert and -ca-path are specified, -ca-path is used. -insecure Do not verify TLS certificate. This is highly not recommended. This is especially not recommended for unsealing a vault. ` return strings.TrimSpace(helpText) }